AWS Tutorials

What is Kubernetes vs. Eks?

Kubernetes is open-source container orchestration. EKS is AWS's managed service for running it. Learn what each does and how ECS compares.

On this page
  1. What is Kubernetes vs. EKS?
  2. What Kubernetes does
  3. What Amazon EKS is
  4. What AWS manages and what you still manage
  5. Is EKS real Kubernetes?
  6. Kubernetes, EKS and ECS compared
  7. Cost, briefly
  8. When to choose which
  9. Next steps

What is Kubernetes vs. EKS?

Kubernetes is open-source software that runs containers across a group of machines. Amazon Elastic Kubernetes Service (EKS) is AWS’s managed service for running Kubernetes. So the two are not competitors. EKS is one way to run Kubernetes on AWS.

What Kubernetes does

Kubernetes decides which machine (node) should run each container, starts replacements when containers fail, scales the number of copies up and down, and routes network traffic to them. It also manages configuration and secrets.

Google created Kubernetes, drawing on its internal cluster manager, Borg. Version 1.0 was released in July 2015, and the project was donated to the Cloud Native Computing Foundation (CNCF). It ships about three minor releases a year. The upstream project supports each release for roughly 14 months.

A Kubernetes cluster has two parts:

  • The control plane holds the API server, the etcd data store, the scheduler and the controller manager. It decides what should run and where.
  • The worker nodes run your containers. Each node runs the kubelet, a network proxy and a container runtime.

What Amazon EKS is

Amazon EKS runs the Kubernetes control plane for you. AWS operates the control plane across several Availability Zones, and it replaces failed control plane components automatically. EKS became generally available in June 2018.

EKS runs standard, CNCF-certified Kubernetes. The same kubectl commands, Helm charts and manifests work on EKS and on other conformant clusters. EKS also connects Kubernetes to AWS services, such as IAM for access control, the VPC networking plugin for pod addresses, and load balancers for services.

What AWS manages and what you still manage

The main difference is who runs each layer:

Layer Self-managed on EC2 Amazon EKS (standard) EKS Auto Mode
Control plane (API server, etcd) You AWS AWS
Worker nodes (operating system, scaling) You You AWS manages the nodes
Your apps, manifests and configuration You You You

Even on EKS, you still configure your workloads, choose instance types or other compute options, and plan upgrades. Upgrades are one minor version at a time. Start with the control plane, then update the nodes and the add-ons.

Is EKS real Kubernetes?

Yes. EKS runs upstream Kubernetes that has passed the CNCF conformance tests, so manifests written for conformant Kubernetes usually run on EKS without changes. EKS is not a fork. The main limit is timing. EKS usually adds a new Kubernetes version a few weeks to a few months after the upstream release.

Kubernetes, EKS and ECS compared

Amazon Elastic Container Service (ECS) is a different orchestrator. It is AWS’s own product, so it is not Kubernetes.

Self-managed Kubernetes Amazon EKS Amazon ECS
What it is Open-source orchestrator you run yourself Managed Kubernetes on AWS AWS’s own container orchestrator
Control plane fee None for the software, but you run the servers $0.10 per hour per cluster None
Portability Runs on many clouds and on-premises Standard Kubernetes APIs, with AWS integrations Specific to AWS
Learning curve Highest Moderate Lower

Cost, briefly

EKS adds a fixed control plane fee, and you pay for the worker nodes and the AWS resources they use. Self-managed Kubernetes avoids that fee but adds operating work. ECS avoids the fee too. The explanation of why EKS is so expensive covers the full bill.

When to choose which

  • Choose EKS when you need Kubernetes features or tooling, want AWS to run the control plane, and can manage the workloads yourself.
  • Choose self-managed Kubernetes when you need full control over the cluster, or need to run the same setup across clouds or on-premises, and have the team to operate it.
  • Choose ECS when you want containers on AWS with the least operational work and do not need Kubernetes APIs.

If you decide on EKS, the EKS setup guide walks through creating a small test cluster and removing it.

Next steps

The complete guide to aws tutorials

AWS Fundamentals: The Core Cloud Computing Services
Read the guide

Keep exploring

Guides from other topics

All topics →