From ea13e0afde0e9bb68a7e96e31dbf6c73b5a2b8db Mon Sep 17 00:00:00 2001
From: Tom Dooner <tomdooner@navapbc.com>
Date: Sun, 25 Aug 2024 20:24:56 -0700
Subject: [PATCH] Upgrade demo env to be three larger containers

This upgrades the demo containers to match production: three ECS
containers with 1 vCPU and 4 GB RAM.

This is temporary, to handle increased load from a lot of scanning
activity will be occurring in the coming days.

The previous (default) values were a single container with 0.25 vCPU and
512 MB RAM.
---
 infra/app/app-config/dev.tf | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/infra/app/app-config/dev.tf b/infra/app/app-config/dev.tf
index dd2084eb..bcb20d09 100644
--- a/infra/app/app-config/dev.tf
+++ b/infra/app/app-config/dev.tf
@@ -10,6 +10,13 @@ module "dev_config" {
   has_database                    = local.has_database
   has_incident_management_service = local.has_incident_management_service
 
+  # These numbers are a starting point based on this article
+  # Update the desired instance size and counts based on the project's specific needs
+  # https://conchchow.medium.com/aws-ecs-fargate-compute-capacity-planning-a5025cb40bd0
+  service_cpu                    = 1024
+  service_memory                 = 4096
+  service_desired_instance_count = 3
+
   # Enables ECS Exec access for debugging or jump access.
   # See https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html
   # Defaults to `false`. Uncomment the next line to enable.