AWS copilot manifests to deploy iloveconference

Deploy nginx, client, and server to a single ECS task running on fargate behind an ALB.

Install

Host your domain in Route53.

Delete .workspace

Run copilot app init --domain <domain> (without www). Name the application; e.g., ilc This creates infrastructure on AWS.

Run copilot init You want a Load Balanced Web Service. Pass in the location of your existing server image.

Delete the directory that copilot created for you and rename the old application directory to your application name.

Change the application name in /addons/cw-access.yml. Make all of the necessary changes to /manifest.yml including updating the ECR locations.

Run copilot env init to initialize a prod environment

Run copilot env deploy --name prod to create more infrastructure.

Run copilot secret init to add the following secrets

• UPSTASH_REDIS_REST_URL
• UPSTASH_REDIS_REST_TOKEN
• OPENAI_API_KEY
• PINECONE_API_KEY
• PINECONE_ENV
• VOYAGE_API_KEY (not currently used)
• COHERE_API_KEY (not currently used)

Usage

Update /manifest.yml with the latest image tags for client and server from the github actions output.

The run copilot deploy

If you need to update a secret, rerun copilot secret init with the --overwrite parameter.