Can Kubernetes be used on AWS?
Yes. AWS is one of the most common places to run Kubernetes. You can use a managed service, run the cluster yourself on EC2 instances, use a Red Hat product that AWS supports, or run an EKS-style cluster on your own hardware.
Option 1: Amazon EKS
Amazon Elastic Kubernetes Service (EKS) is AWS’s managed Kubernetes service. AWS runs the control plane, which includes the API server and etcd, across several Availability Zones. You pay a fixed fee of $0.10 per hour for each cluster, plus the compute and other resources your workloads use.
For worker nodes, you can use managed node groups, self-managed nodes, AWS Fargate for serverless pods, or EKS Auto Mode, which manages more of the node layer. The EKS setup guide shows how to create a test cluster.
Option 2: Self-managed Kubernetes on EC2
You can install Kubernetes on EC2 instances with tools such as kOps, kubeadm, k3s or RKE2 (from Rancher). This gives you full control over the version, the configuration and the add-ons.
The trade-off is operating work. A highly available control plane usually needs three control plane nodes (or five) for etcd quorum. You also manage etcd backups, certificates, upgrades and recovery. Autoscaling is usually handled by the Cluster Autoscaler or Karpenter.
Option 3: Red Hat OpenShift Service on AWS (ROSA)
Red Hat OpenShift Service on AWS (ROSA) is an OpenShift platform, which is built on Kubernetes. Red Hat and AWS both support it. It suits teams that already use OpenShift tools, or that want a platform with more built-in features and a joint support model.
Option 4: EKS Anywhere
EKS Anywhere lets you run EKS-style clusters on your own hardware, in your data center. It suits organizations with on-premises requirements that still want the same Kubernetes tooling they use on AWS.
Comparing the options
| Option | Who runs the control plane | Who runs the worker nodes | Best fit |
|---|---|---|---|
| Amazon EKS | AWS | You (or Auto Mode and Fargate) | Most AWS teams that want managed Kubernetes |
| Self-managed on EC2 | You | You | Teams that need full control and have the operating capacity |
| ROSA | Red Hat and AWS | Shared, per the service terms | Teams that use OpenShift |
| EKS Anywhere | You, on your hardware | You | On-premises workloads with EKS tooling |
The hidden cost of self-managing
Running Kubernetes yourself does not avoid cost. You pay for EC2 instances for the control plane, and those nodes need backups, patches and monitoring. The engineering time to run the cluster is often the largest cost. Compare the whole picture, not only the EKS control plane fee of about $73 a month.
Learn locally before you pay for AWS
Before you create a managed cluster, practice on your own computer. Tools such as kind, minikube and k3d run small Kubernetes clusters locally. You can learn kubectl, deployments, services and configuration without an AWS bill. Move to EKS when you are ready to test the AWS integrations, such as IAM access and load balancers.
Next steps
- Read the Kubernetes vs. EKS explainer to see how the two relate.
- Follow the EKS setup guide for a step-by-step test cluster, with the teardown steps.
- Read why EKS can be expensive before you leave a cluster running.
- If you do not need Kubernetes, the ECS container deployment guide shows a simpler AWS option.