Amazon EKS on AWS Local Zones - Amazon EKS

Amazon EKS on AWS Local Zones

An AWS Local Zone is an extension of an AWS Region in geographic proximity to your users. Local Zones have their own connections to the internet and support AWS 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 running certain infrastructure. This includes Amazon EC2 instances, Amazon EBS volumes, and Application Load Balancers (ALBs) from a Local Zone as part of your cluster. We recommend that you consider the following when using Local Zone infrastructure as part of your Amazon EKS cluster.

Kubernetes versions

Only Amazon EKS clusters that run Kubernetes versions 1.17 and later can use Local Zone compute resources.


You can't create managed node groups in AWS Local Zones with Amazon EKS. However, you can create self-managed nodes in AWS Local Zones using the Amazon EC2 API, AWS CloudFormation, or eksctl. For more information, see Self-managed nodes.

Network architecture

The Amazon EKS managed Kubernetes control plane always runs in the AWS 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 AWS 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.

After the cluster is created, tag your Local Zone subnets with the Amazon EKS cluster name. For more information, see Subnet tagging. You can then deploy self-managed nodes to the Local Zone subnets and the nodes join your Amazon EKS cluster.