Run a containerized API.
Scale by task without patching or managing the capacity of EC2 container hosts.
Which choice is most appropriate?
Run the containers on Amazon ECS with the Fargate launch type so AWS manages the underlying servers while the service scales tasks.
Detailed explanation
Fargate runs ECS tasks without requiring the customer to provision or patch container hosts.
Fargate runs ECS tasks without requiring the customer to provision or patch container hosts.
Route 53 provides DNS and does not run container tasks.
Route 53 provides DNS and does not run container tasks.
Dedicated servers add host and capacity management that the requirement seeks to avoid.
Dedicated servers add host and capacity management that the requirement seeks to avoid.
S3 stores objects and is not a container execution environment.
S3 stores objects and is not a container execution environment.
Check official documentation
Compare the following points with the official documentation.
Amazon ECS Fargateの公式説明を確認する。
What to confirm
コンテナ実行とホスト管理の責任分界を説明できる。
Key points
- Amazon ECS
- Fargate
- Container task
Notes
- Environment: AWS公式ECSドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Serverless container boundary
Fargate removes host capacity and patching work while the customer still defines task resources and deployment behavior.
Operational responsibility
Choosing Fargate does not remove the need to secure images, task roles, and application settings.