Amazon EKS and Amazon Local Zones - Amazon EKS
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon EKS and Amazon Local Zones


This capability is not available in China Amazon Web Services Regions.

An Amazon Local Zone is an extension of an Amazon Web Services Region in geographic proximity to your users. Local Zones have their own connections to the internet and support Amazon Direct Connect. Resources created in a Local Zone can serve local users with low-latency communications. For more information, see Local Zones.

Amazon EKS supports certain resources in Local Zones. This includes 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 managed node groups or Fargate nodes in Local Zones with Amazon EKS. However, you can create self-managed Amazon EC2 nodes in Local Zones using the Amazon EC2 API, Amazon CloudFormation, or eksctl. For more information, see Self-managed nodes.

Network architecture
  • The Amazon EKS managed Kubernetes control plane always runs in the Amazon Web Services 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 Web Services Region or Local Zone using Amazon EKS managed elastic network interfaces. To learn more about Amazon EKS networking architecture, see Amazon EKS networking.

  • 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.