EKS Networking: VPC and Subnets
What You'll Learn
You'll understand how Amazon EKS integrates with AWS Virtual Private Clouds and the specific subnet requirements for running your control plane and worker nodes.
The VPC Foundation
Think of an AWS VPC (Virtual Private Cloud) as the network foundation for your EKS cluster—it's like the building where your Kubernetes infrastructure lives. EKS doesn't create networking from scratch; instead, it integrates directly with your existing VPC, using AWS networking primitives to connect and secure your cluster components.
Subnet Requirements
EKS has specific subnet expectations for proper operation:
Control Plane Subnets
When you create an EKS cluster, you specify at least two subnets in different Availability Zones for the control plane. AWS manages these Elastic Network Interfaces (ENIs) in your subnets to communicate with your worker nodes. These subnets can be private or public, but private is recommended for security.
Worker Node Subnets
Your worker nodes (EC2 instances or Fargate pods) run in subnets you designate. These can be the same subnets as the control plane or different ones. Private subnets are strongly recommended for worker nodes to minimize exposure.
The Integration Picture
Here's how it works: EKS places network interfaces in your VPC subnets, allowing the control plane (managed by AWS) to communicate with your worker nodes (in your account). Your VPC's route tables, security groups, and network ACLs all apply—EKS respects your existing network architecture.
Key difference from self-managed Kubernetes: You don't provision the control plane's infrastructure yourself. You simply tell EKS which subnets to use, and AWS handles the networking complexity behind the scenes.
Key Takeaway: EKS requires a VPC with at least two subnets across different Availability Zones; the control plane uses ENIs in these subnets to communicate securely with worker nodes, all within your VPC's network boundaries.