AWS now fully supports Kubernetes with the general release of Amazon EKS, following other cloud vendors, after announcing the service last year at AWS re:Invent
Tom Krazit / GeekWire :
Context & Ripple Effects
This closes a loop AWS opened over the past year: it joined the Cloud Native Computing Foundation as a platinum member in August 2017, taking a board seat in the body that hosts Kubernetes, then announced EKS at re:Invent that November. The general release brings AWS to parity with rival clouds that already ran managed Kubernetes.
The significance is strategic rather than technical — AWS, long the holdout behind its own Elastic Container Service, is conceding that Kubernetes is the layer customers want standardized. That concession set up the hybrid plays that followed, including Cisco's partnership to run hybrid Kubernetes on AWS later that year.
First-order effects
- AWS customers can now run production workloads on managed Kubernetes instead of waiting on the preview, removing the main reason to look at Google Cloud or Azure for container orchestration.
- AWS's own Elastic Container Service is effectively demoted to the alternative option, since EKS becomes the default answer for Kubernetes-standardized shops on AWS.
Second-order effects
- Hybrid-cloud vendors move fast to attach to the newly available service — Cisco's Kubernetes-on-AWS partnership lands within months, and VMware's existing AWS alliance gives enterprises another path to run Kubernetes across data centers and AWS.
- Rival clouds lose the managed-Kubernetes differentiator they held while EKS was preview-only, pushing competition toward price, integration depth, and multi-region maturity rather than mere availability.
Third-order effects
- Once AWS treats Kubernetes as neutral infrastructure rather than a competitor to its own orchestrator, the door opens to running EKS outside AWS entirely — a path the corpus shows AWS took by 2020 with ECS Anywhere and EKS Anywhere running on Azure or Google Cloud.
- Kubernetes consolidates as the industry's de facto portability layer, which structurally weakens any single cloud's lock-in at the orchestration tier and shifts vendor differentiation down into proprietary services layered on top.
The trend: Cloud providers are converging on Kubernetes as the shared control plane for containers, with AWS moving from holdout to steward to, eventually, exporting its managed Kubernetes beyond its own cloud.