Basic Information
| Field | Details |
|---|---|
| English name | Amazon EKS |
| Full name | Amazon Elastic Kubernetes Service |
| Chinese description | 托管 Kubernetes 服务 |
| Japanese description | Amazon EKS（マネージド Kubernetes サービス） |
| Exam frequency | ⭐⭐⭐⭐ |
| Often confused with | ECS / Kubernetes / Fargate |
In one sentence
AWS-managed Kubernetes for running workloads that need Kubernetes APIs, tooling, and ecosystem compatibility.
Key points
- AWS manages the Kubernetes control plane; users still design workloads, networking, permissions, upgrades, and nodes.
- Worker capacity can use EC2 managed node groups or Fargate.
- Choose EKS when Kubernetes compatibility or an existing K8s platform matters.
Exam takeaway
Choose ECS first when an AWS-native, simpler orchestration model is sufficient.
Update: nodes and storage
- A managed node group automates EC2 worker-node provisioning and lifecycle, but the underlying capacity is still EC2 plus an Auto Scaling group.
- EKS Auto Mode manages additional EC2 infrastructure from pod requirements; it is different from the Fargate no-node-group model.
- A CSI driver connects StorageClass/PVC requests to EBS or EFS. The driver is an integration layer, not storage itself.