Help improve this page
Want to contribute to this user guide? Choose the Edit this page on GitHub link that is located in the right pane of every page. Your contributions will help make our user guide better for everyone.
Launch low-latency EKS clusters with Amazon Local Zones
An Amazon Local Zone
Amazon EKS supports certain resources in Local Zones. This includes managed node groups, self-managed Amazon EC2 nodes, Amazon EBS volumes, and Application Load Balancers (ALBs). We recommend that you consider the following when using Local Zones as part of your Amazon EKS cluster.
-
You can’t create Fargate nodes in Local Zones with Amazon EKS.
-
The Amazon EKS managed Kubernetes control plane always runs in the Amazon Region. The Amazon EKS managed Kubernetes control plane can’t run in the Local Zone. Because Local Zones appear as a subnet within your VPC, Kubernetes sees your Local Zone resources as part of that subnet.
-
The Amazon EKS Kubernetes cluster communicates with the Amazon EC2 instances you run in the Amazon Region or Local Zone using Amazon EKS managed elastic network interfaces. To learn more about Amazon EKS networking architecture, see Configure networking for Amazon EKS clusters.
-
Unlike regional subnets, Amazon EKS can’t place network interfaces into your Local Zone subnets. This means that you must not specify Local Zone subnets when you create your cluster.