What is Amazon EKS? A plain-English explainer
Amazon EKS, short for Elastic Kubernetes Service, is managed Kubernetes on AWS — AWS operates the Kubernetes control plane for you, while your team runs containerised applications on top of it using the same open-source Kubernetes tools and APIs used anywhere else. Kubernetes itself is powerful but operationally heavy to run yourself, since the control plane is a set of components that must be kept highly available, patched and scaled in its own right, before a single application container has even started. EKS removes that operational burden while keeping the Kubernetes experience intact, which is the whole appeal for teams that specifically want Kubernetes rather than an AWS-native alternative. Here is what Kubernetes brings to the table, what “managed” actually removes from your plate, and how EKS relates to its simpler AWS sibling, ECS.
A quick word on Kubernetes
Kubernetes is an open-source system for orchestrating containers — deciding where they run, keeping the desired number healthy, and handling networking and scaling between them. Our what-is-kubernetes explainer covers it properly; the short version here is that Kubernetes is not tied to any one cloud provider, which is exactly why it needs a name of its own inside AWS rather than just being “how AWS runs containers”.
That portability is Kubernetes’ main selling point: the same manifests and tooling that work on EKS also work on Azure’s AKS, Google’s GKE, or a self-managed cluster, which matters to teams running multi-cloud or hybrid environments, or simply hiring from a large existing Kubernetes talent pool.
What “managed” actually adds
Running Kubernetes yourself means standing up and operating the control plane — the components that track cluster state, schedule workloads and expose the Kubernetes API — and keeping it highly available and patched, on top of everything an application itself needs. That is real, ongoing operational work before any application logic is involved.
With EKS, AWS runs and scales that control plane for you and keeps it patched and highly available, integrated with AWS networking, identity and logging. You still define and manage the workloads that run on the cluster using standard Kubernetes tooling; EKS removes the control-plane operations layer underneath it, not the Kubernetes concepts themselves.
EKS vs ECS
AWS offers two container orchestrators, and EKS is the Kubernetes one. Our what-is-amazon-ecs explainer covers the other: ECS is AWS’s own, simpler orchestrator with concepts specific to AWS, built for teams that want to run containers on AWS without taking on Kubernetes at all. EKS is the choice when you specifically need Kubernetes — because of portability across clouds, existing team expertise, or reliance on tools built for the Kubernetes ecosystem.
Our docker-vs-kubernetes explainer covers the broader orchestration decision in more depth; EKS and ECS are simply AWS’s two answers to it, one Kubernetes-based and one AWS-native.
When you would choose EKS
EKS suits teams that already use Kubernetes elsewhere, need to move workloads between cloud providers or on-premises, or want access to the wider Kubernetes ecosystem of tools and add-ons. It is a heavier choice than ECS if none of that applies — Kubernetes brings its own concepts and learning curve, even with the control plane managed for you.
How EKS fits across clouds
EKS is AWS’s managed Kubernetes offering, sitting alongside Azure Kubernetes Service (AKS) and Google Kubernetes Engine (GKE) as each major provider’s equivalent. The underlying Kubernetes concepts transfer between all three; what differs is how each provider wires the control plane into its own networking, identity and billing.
Pricing model, and where EKS appears in certification study
EKS is billed on a consumption basis — you pay for the managed control plane plus whatever compute your worker nodes actually use, rather than any upfront licence. Exact rates and options change, so treat that as the model rather than a figure and check AWS’s own pricing page for current numbers.
Kubernetes is the whole subject of the Kubernetes and Cloud Native Associate (KCNA) exam, and EKS specifically shows up in the AWS Developer Associate and Solutions Architect Associate exams as the managed-Kubernetes option alongside ECS. As with the other services covered here, this article stays introductory — how EKS clusters are actually configured, networked and operated is exam-depth material our /revision study library is built to cover.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.