Containers
RecognitionAmazon Elastic Kubernetes Service (Amazon EKS)
Managed Kubernetes service for running Kubernetes applications on AWS.
Key points
- Container images, manifests, resource requests, configuration, and probes contribute to a deployable application.
- Readiness controls whether a pod should receive service traffic.
- DVA-C02 does not require Kubernetes cluster, node, or networking administration.
Best-known use cases
- Deploy an approved containerized application to an existing Kubernetes environment.
- Apply application readiness and resource configuration.
What candidates often confuse it with
- EKS uses Kubernetes APIs; ECS uses AWS-native task and service APIs.
- Readiness indicates traffic eligibility; process liveness indicates whether the container should be restarted.
Key takeaway
Recognize EKS at application packaging, deployment, and readiness depth only.
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)
- D4.2 — Instrument code for observability
- 4.2.8 — Configure application health checks and readiness probes