/Glossary · AWS
What is Amazon EKS?
Amazon EKS (Elastic Kubernetes Service) is the AWS managed service for running Kubernetes without operating the control plane. AWS handles control plane availability and upgrades, and you deploy your workloads with standard Kubernetes tooling.
How Amazon EKS works
EKS runs the Kubernetes control plane across multiple Availability Zones. Worker nodes can be EC2 managed node groups, Fargate profiles or EKS Auto Mode, which hands node provisioning, scaling and upgrades to AWS, along with components like networking and storage.
EKS integrates with IAM through EKS Pod Identity for per-pod permissions, with Elastic Load Balancing through the AWS Load Balancer Controller, with EBS and EFS for storage and with CloudWatch for observability. Karpenter, the open source node autoscaler backed by AWS, picks instances based on actual pod demand.
When Amazon EKS makes sense
It fits when your team already knows Kubernetes, when you need portability across environments, or when the Kubernetes ecosystem adds concrete value: operators, Argo CD, a service mesh or GPU-based machine learning workloads. It is also a solid foundation for an internal platform that serves many teams.
If you have a handful of services and a small team with no Kubernetes experience, Amazon ECS is usually simpler to operate. EKS charges an hourly fee per cluster and requires keeping versions, add-ons and policies up to date, an operational cost you should account for from the start.
Best practices and common mistakes
Define clusters with Terraform, deploy applications with GitOps, use Pod Identity instead of credentials stored in secrets, and enforce policies with Kyverno or OPA Gatekeeper. Plan Kubernetes version upgrades every few months: versions have limited standard support, and extended support costs extra.
Common mistakes: creating one cluster per application and multiplying cost and maintenance, not setting resource requests and limits, exposing the API server endpoint publicly without restrictions, and staying on old versions until upgrading turns into a risky project.
/FAQ
Questions about Amazon EKS
Another question? Write to hello@nubent.com and an engineer will answer.
What is the difference between EKS and ECS?
EKS runs standard Kubernetes, with its tooling and portability, but requires more expertise and maintenance. ECS is AWS's own orchestrator, simpler and tightly integrated with the rest of AWS. For small teams, ECS is usually faster to adopt.
What is EKS Auto Mode?
It is an EKS operating mode where AWS manages the compute nodes, their scaling with Karpenter technology, security patching, and components like pod networking, load balancing and block storage. It removes a large share of the cluster's operational work.
How much does Amazon EKS cost?
You pay an hourly fee per cluster on standard support, higher on extended support, plus the compute your nodes use, whether EC2, Fargate or Auto Mode, which adds a charge per managed instance. Savings Plans and Spot Instances help lower compute cost.
How we help with Amazon EKS
Kubernetes on Amazon EKS
Amazon EKS clusters with Karpenter, Helm and Argo CD, pod-level security and zero-downtime upgrades, run through Terraform and GitOps.
Learn morePlatform Engineering
An internal developer platform on AWS with golden paths, Backstage and Terraform self-service, for autonomous teams that ship quickly and safely.
Learn moreCloud modernization
AWS application modernization: from mutable servers and monoliths to containers, serverless and managed services, in stages and without stalling the product.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.