Key points

• Task definitions bind an image, resources, roles, configuration, and health behavior.
• Task roles supply application credentials; execution roles support ECS control-plane actions such as image and log access.
• Health and deployment behavior matter here, not cluster or server administration.

Best-known use cases

• Run containerized application services.
• Deploy approved task-definition revisions with health checks.

What candidates often confuse it with

• ECS runs containers with AWS-native orchestration; EKS provides managed Kubernetes control planes.
• A task definition configures a workload; ECR stores its image artifact.

Key takeaway

Recognize ECS as the application container runtime and keep task identity, revision, resources, and readiness explicit.

Related services

• Amazon Elastic Container Registry (Amazon ECR)
• Elastic Load Balancing
• Amazon CloudWatch

Relevant exam tasks

• D3.1 — Prepare application artifacts to be deployed to AWS
• 3.1.4 — Apply application requirements for resources (for example, memory, cores)
• D3.3 — Automate deployment testing
• 3.3.3 — Create application environments that use approved versions for integration testing (for example, Lambda aliases, container image tags, AWS Amplify branches, AWS Copilot environments)
• D4.2 — Instrument code for observability
• 4.2.8 — Configure application health checks and readiness probes

Learn more

• Amazon Elastic Container Service (Amazon ECS)