AWS ECS Integration

[joshuabrink]

Step-by-step AWS ECS integration guide.

• Currently there is only AWS CLI commands steps. UI guide might be worth including.
• Only included MongoDB setup on on initial pass - Postgres to be added.
• Included potential future todos.

Overview

• Bucket storage setup (MongoDB Atlas or self-managed)
• Source database configuration for replication
• VPC, security groups, and NAT gateway configuration
• Application Load Balancer setup with SSL/TLS and WebSocket support
• Secrets Manager integration
• ECS task definitions, cluster creation, and service deployment

[rkistner]

Happy with new doc now, but it wasn't my intention to update our base recommendations.

To make the two consistent, perhaps we could recommend this?

1. Minimal for development: 512MB memory, 1 vCPU (or less if supported).
2. Base recommendation for production: 1GB memory, 1 vCPU per container.
3. Safe recommendation for production (supports larger rows, higher load): 2GB memory, 2 vCPU per container.

The same recommendations apply for both replication and API containers.

For the ECS guide, we can default to the "safe" recommendation. Not sure if there's a better term for that?

[michaelbarnes]

Sorry about the confusion there. I've made the last few tweaks as suggested. I think it looks good, but one last check on your end would be good.