🐳
ECS Fargate Microservice
ALB → ECS Fargate service (2 tasks) with execution + task IAM roles, plus RDS PostgreSQL.
What you can build with this
Run a containerized service without managing EC2 instances or patching an OS — Fargate handles the compute. The task definition ships with the public nginx image as a deploy-clean placeholder so the stack reaches CREATE_COMPLETE immediately; swap in your own image before real traffic. The database host/port reach the container automatically via environment variables (no manual wiring).
Deployment timing
After you run the deploy command, resources come online at different times. Check the validation steps in order.
| Resource | Ready in |
|---|---|
| VPC, subnets, security groups | 1–2 min |
| NAT Gateway (both AZs) | 2–4 min |
| Load Balancer | 2–3 min |
| ECS tasks running (placeholder image) | 2–3 min |
| RDS Database available | 5–10 min |
DNS / Certificate note: The load balancer DNS name is the correct Route53 alias target. HTTPS requires a Certificate ARN set on the ALB node before export; the exported default is HTTP-only.
CloudFormation parameters
These are the values you will fill in when deploying the exported template. Changing these does not break the template — that is the point.
| Parameter | What to provide | Example |
|---|---|---|
| Environment | Environment tag applied to resources (does not rename them) | dev |