trial/dan-1292-create-infra-scripts-to-automate-the-deployment-onto-ecs

[trial-danswer]

Description

• Adds cloudformation templates, parameter json files, deploy script, uninstall script, parameterized postgres pg_hba.conf file, and added env variables to the run_nginx.sh script.
• The deploy script is idempotent in that it checks if the stack already exists then moves onto deploying the next stack in the array.
• This deploys a lambda function that is scheduled to restart the ECS Services on a nightly basis. Furthermore, it can be invoked directly via the command line...and the scheduling can be disabled. This will streamline the process of ensuring that onyx apps are up-to-date.

How Has This Been Tested?

Steps

• Ensure to update the parameter.json files as needed, the defaults work with the trial AWS account. VpcID and SubnetIDs are unique to AWS account.
• The deploy.sh script requires installed envsubst or directly updating pg_hba.conf to replace the value ${ECS_FARGATE_VPC_CIDR} with the AWS account VPC CIDR IPv4 value.
• Run the deploy script all the way through to confirm that it works . I used the following command./deploy 172.31.0.0/16.

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
internal-search	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 21, 2025 10:08pm

[trial-danswer]

I've updated the PR with changes to include horizontal auto-scaling of tasks based on cpu and memory for api-backend, background, model-servers, and web-server. Additionally, I've updated the templates to accept parameters for task memory, cpu, and desired count. Lastly, I set the default memory & cpu for tasks based on approx values from the Kubernetes helm-charts. The ECS Fargate mem/cpu values are based on the following table: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-cpu-memory-error.html