AWS is the dominant cloud provider, but it lagged behind Google and Microsoft in Kubernetes support. EKS changes that — and we got into the preview program.
Why EKS Took So Long¶
Amazon had ECS — their own container orchestration. Investing in Kubernetes meant admitting that proprietary solutions weren’t enough. But the community decided clearly: Kubernetes won.
How EKS Differs from GKE¶
Networking: EKS uses Amazon VPC CNI plugin — every pod gets a real VPC IP. Native integration with security groups, ALB. But there’s a limit on the number of pods per node.
IAM Integration: Service accounts can directly assume IAM roles — no sharing of AWS credentials. Excellent for security.
What’s Missing in EKS (For Now)¶
- Fargate integration — promised for later
- Managed node groups — you manage worker nodes yourself
- More expensive — $0.20/hour for control plane (~$150/month)
Why EKS Is Important¶
Most of our clients are on AWS. With EKS, we can offer them Kubernetes without needing to leave the AWS ecosystem. Integration with ALB, CloudWatch, IAM, ECR — all of this is native.
EKS Is a Game Changer for AWS Customers¶
For our AWS clients, this is the natural path to Kubernetes. We’re looking forward to the GA release and managed node groups.
Need help with implementation?
Our experts can help with design, implementation, and operations. From architecture to production.
Contact us