This project contains the AWS Cloud Development Kit (CDK) stack for deploying the Open Chat Studio infrastructure.
- Architecture Overview
- Project Structure
- Quickstart
- First Time Deployment Steps
- Steady State Deployment Steps
- Connecting to Running Services
- Adding Environment Variables
- Other Useful CDK Commands
- Troubleshooting
The architecture consists of various AWS components:
- RDS PostgreSQL database
- Elasticache Redis
- Elastic Container Registry (ECR)
- ECS Fargate services for the Django application, including:
- Django web service:
- Runs two containers: one for executing migrations and another for running the Gunicorn server.
- The migrations container runs first and the Gunicorn container starts afterward.
- The service is behind an Application Load Balancer (ALB) with a health check target group.
- Celery worker service
- Celery beat service
- Django web service:
Additional components set up by this project include:
- VPC with public and private subnets
- Load balancer for the Django service
- S3 buckets for media files
- Certificate Manager certificates for domain management
- Email identity verification for the domain
- GitHub Actions roles for the CI/CD pipeline
- Secrets Manager for storing Django secrets
This section describes the layout of the project:
ocs_deploy/cli/*.py
: Scripts for deploying CDK stacks and managing secrets.- Run
ocs -l
to see available tasks.
- Run
cdk.json
: Configuration file for the CDK Toolkit.ocs_deploy/
: Contains the CDK stack definitions.
This guide assumes you have uv installed.
$ uv venv
$ uv pip install -e .
$ source .venv/bin/activate
$ ocs -l
$ ocs init <env>
Edit the generated .env.{env name}
file to set your required configurations.
- You have an AWS account with the necessary permissions and configured SSO.
- You have the correct AWS profile set:
export AWS_PROFILE=XXX
- SSO credentials are configured (
aws configure sso
). - You have permissions to create resources in the account.
- For new environments, run:
ocs --env <env> aws.bootstrap
-
Set Up the ECR Repository
ocs --env <env> aws.deploy -s ecr -v
Next, push the initial version of the Docker image to the registry:
export AWS_ACCOUNT_ID=xxx \ && export AWS_REGION=us-east-1 \ && export OCS_ENV=<env> \ && export OCS_NAME=<name> \ && export REGISTRY=$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com \ && export IMAGE=$REGISTRY/$OCS_NAME-$OCS_ENV-ecr-repo docker build . -t "$IMAGE:latest" -f Dockerfile.web aws ecr get-login-password --region $AWS_REGION | docker login --username AWS --password-stdin $REGISTRY docker push "$IMAGE" --all-tags
For more details on Docker image pushing, visit the AWS ECR documentation.
-
Set Up RDS, Redis, and S3
ocs --env <env> aws.deploy --stacks ec2tmp,rds,redis,s3
-
Set Up Domains and GitHub Roles
ocs --env <env> aws.deploy --stacks domains,github
- Create DNS entries for domain and email domain verification.
- CNAME records will be provided in the stack output.
-
Create Necessary Secrets
ocs --env <env> secrets.create-missing
-
Set Up the Django Service
ocs --env <env> aws.deploy --stacks django
After the initial deployment, you can deploy any stack independently. Typically, you will only run the CDK deploy when changing infrastructure. For code deployments, use the GitHub Actions defined in the Open Chat Studio repository.
To connect to a running service, use the ocs connect
command:
ocs --env <env> connect # Default command is /bin/bash
ocs --env <env> connect --command "python manage.py shell"
- Add the variable to
.env.<env>
and.env.example
. - Update the
ocs_deploy.config.OCSConfig
class with the new variable. - Update the
ocs_deploy/fargate.py
file to include the variable in theenv_dict
method.
Deploy the Django service to apply changes:
ocs --env <env> aws.deploy --stacks django
-
Add the secret's name to the
ocs_deploy/secrets.yml
. -
Set the secret value:
ocs --env <env> secrets.set SECRET_NAME SECRET_VALUE
After setting, deploy the Django service to include the new secret:
ocs --env <env> aws.deploy --stack django
cdk ls
: List all stacks in the app.cdk synth
: Emit the synthesized CloudFormation template.cdk deploy
: Deploy the stack to your default AWS account/region.cdk diff
: Compare the deployed stack with the current state.cdk docs
: Open CDK documentation.
Common Issues
- AWS Credentials Not Set: Ensure that your AWS credentials are correctly configured and that AWS_PROFILE is set.
- Docker Login Issues: If you encounter issues with Docker login, ensure that you are using the correct AWS region and account ID.
- Secrets Not Found : If a secret is not found, ensure that it is correctly defined in the secrets.yml file and that it has been created in AWS Secrets Manager.
For more detailed troubleshooting, refer to the AWS CDK documentation.