Basic Information
| Field | Details |
|---|---|
| English name | Amazon ECS |
| Full name | Amazon Elastic Container Service |
| Chinese description | AWS 原生容器编排服务 |
| Japanese description | Amazon ECS（コンテナオーケストレーションサービス） |
| Exam frequency | ⭐⭐⭐⭐⭐ |
| Often confused with | EKS / Fargate / ECR |
In one sentence
AWS-native container orchestration for deploying, scheduling, scaling, and maintaining container workloads.
Key points
- Task Definition is the run template, Task is one execution, Service maintains desired tasks, and Cluster groups capacity.
- ECS can run on EC2 for more control or on Fargate to avoid managing servers.
- Images are stored in ECR; EC2 or Fargate supplies compute while ECS performs orchestration.
Exam takeaway
A common path is code → image → ECR → Task Definition → ECS Service → ALB and Auto Scaling.
Update: roles and capacity providers
- A task role authorizes application code in the container. A task execution role lets the ECS agent pull ECR images, publish logs, and retrieve startup secrets.
- A capacity provider defines whether tasks obtain compute from Fargate, Fargate Spot, or an Auto Scaling group.
- In a strategy, Base is the minimum initial allocation and Weight controls relative distribution of the remaining tasks; neither is a fixed percentage.