Closed Maveric-k07 closed 1 month ago
@Maveric-k07 Thanks for taking this up. The code looks good in the first skim.
Can you add the steps that you mentioned in this issue to run the script in the docs
folder as the file setting-up-in-aws.md
file?
@arpitbbhayani I have created a new docs folder and added the setting-up-in-aws.md
. Please take a look. I have also talked about an issue I am facing with the connection being timed-out after the first test; can you also take a look at that.
When you create a stack it will prompt you to enter a passphrase as follows: Enter your passphrase to unlock config/secrets (set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember); you can simply hit enter if you dont want to skip remembering a passphrase.
Pulumi.dev.yaml is the config example for a stack called "dev" that i have created which has the you can use when you create a new one.
The private_key for ssh-ing into the instance will be stored in AWS parameter store
Add Pulumi script to automate the deployment of DiceDB on AWS.
How to Run the Script
Configure AWS credentials:
Create and activate a virtual environment:
Install requirements:
Create a new Pulumi stack or use an existing one:
Review and update inputs in the Pulumi config file (
Pulumi.<stack-name>.yaml
)Preview the changes:
Deploy the infrastructure:
Implementation Details
Testing Results
The deployment successfully creates the infrastructure and installs DiceDB. However, there's a connectivity issue:
systemctl status dicedb
shows the service as active and runningtest script:
Test Script Output
I'd appreciate any insights or suggestions on addressing the connection timeout issue, as well as any improvements to the infrastructure setup or DiceDB configuration.
Note on S3 Backend
This Pulumi project uses an S3 backend for state management. Important: Ensure that the specified S3 bucket (
dice-pulumi
/any suitable bucketname) is created before running the Pulumi script. Alternatively we can use the pulumi cloud for storing the state.