Four ways to run EKS-flavoured Kubernetes, from AWS-managed to your own hardware.
Newer features let you buy more control-plane capacity, or bring your own machines under an EKS control plane.
AWS-run control plane that scales automatically; nodes in your AWS VPC. The default for most teams.
Pick a capacity tier for the API and scheduler for predictable performance at very large or bursty scale, such as big AI jobs. Higher price.
Your on-premises or edge machines join an EKS cluster as nodes, billed per vCPU-hour, with the control plane in AWS.
AWS's Kubernetes distribution that you run yourself on your hardware. Closer to kubeadm or RKE2 in ownership.
Shopwave's choice
Standard EKS for orders and loyalty in eu-west-1. Warehouses stay on k3s managed by Rancher (Deck 4). Hybrid Nodes is on the review list if the warehouses get reliable links.
Verify before you commit
These offerings are newer and evolving. Confirm availability, regions, network requirements and pricing in the current AWS documentation.