Amazon ECS Execution Architecture and Selection Criteria – Part 2: Deployment Strategies, Networking, and Design Limits

The Amazon ECS deployment controller is categorized into three types: ECS, CodeDeploy, and External, supporting a total of 6 deployment strategies. In addition to the default Rolling strategy, options for gradual traffic shifting such as Blue/Green, Linear, and Canary are provided, with AWS recommending the use of built-in Blue/Green over the existing CodeDeploy method.

In terms of network configuration, awsvpc mode is the recommended mode supported on both Linux and Windows, and Fargate can only use this mode. Inter-service connectivity can be implemented via Service Connect or Cloud Map, while App Mesh is excluded as support is scheduled to end on September 30, 2026. Regarding storage, various volume options such as EFS, EBS, and S3 are provided, but some features of Docker volume and bind mount are restricted to EC2 only.

In terms of performance and operations, an improvement was applied as of June 18, 2026, reducing the service auto-scaling scale-in time from 363 seconds to 86 seconds. However, the new Task startup time is listed as 72 seconds to 109 seconds in the original text, requiring contextual verification. Additionally, for Fargate, the vCPU quota (default 6) may be reached before the Task count limit, so requesting a quota increase before large-scale deployments is recommended.