Containers
CoreAmazon EKS
Explicit CloudWatch-agent workload and current target-candidate container context.
Key points
- EKS is a Kubernetes workload surface for telemetry, container scaling, placement, and cluster-capacity evidence.
Best-known use cases
- D1.1, D2.1, and D3.1: collect signals or scale an EKS workload while verifying pod placement and underlying compute capacity.
What candidates often confuse it with
- EKS provides the Kubernetes operating surface; ECR stores images and ECS provides a different container control plane.
Key takeaway
A pod-scaling decision is incomplete until the cluster has capacity and permissions to place the new workload.
Related services
- Amazon ECR
- Amazon ECS
Relevant exam tasks
- D1.1 — Task 1.1: Implement metrics, alarms, and filters by using AWS monitoring and logging services.
- 1.1.1 — Use AWS services (for example, Amazon CloudWatch, AWS CloudTrail, Amazon Managed Service for Prometheus) to configure monitoring and logging for workloads (for example, serverless, compute, AI).
- D2.1 — Task 2.1: Implement scalability and elasticity.
- 2.1.1 — Configure and manage scaling mechanisms in compute environments.
- D3.1 — Task 3.1: Provision and maintain cloud resources.
- 3.1.1 — Create and manage AMIs and container images (for example, EC2 Image Builder).