Fargate overview
This path runs ECS services on Fargate behind an ECS Gateway. It uses the shared VPC and IAM roles from Setup, then builds everything else for this path alone. There is no EC2 capacity to manage.
You deploy two demo apps — Orders (service -a) and Catalog (service -b) — so each managed hostname clearly shows which service the shared ALB routed to.
Architecture (high level)
Section titled “Architecture (high level)”🌐 Internet
Public subnets
Private subnets
service -a · Fargate awsvpc task
service -b · Fargate awsvpc task
NAT gateway → Internet
| Piece | Who owns it |
|---|---|
| VPC, public/private subnets, NAT, gateway infra role, task execution role | Shared setup |
| Cluster, gateway, services | This path (${NAME}-fargate) |
Platform creates the gateway on the public subnets and associates the cluster. Application services only add a gateway connector and place tasks in the private subnets with assignPublicIp=DISABLED. Image pulls and logs go out through NAT.