EKS VPC Requirements Checklist

EKS VPC Requirements Checklist A workflow diagram generated by Archify. 01 / VPC prerequisites 02 / Internet access path Provision subnets · Two or more AZs · VPC prerequisites Provision subnets Two or more AZs Size IP space · nodes × max pods · VPC prerequisites Size IP space nodes × max pods Enable DNS · Hostnames · resolution · VPC prerequisites Enable DNS Hostnames · resolution Internet access · Nodes need egress · VPC prerequisites Internet access Nodes need egress Ready to create · Requirements met · VPC prerequisites Ready to create Requirements met NAT Gateway · Recommended for private subnets · Internet access path NAT Gateway Recommended for private subnets Internet Gateway · Public Subnet · Internet access path Internet Gateway Public Subnet Private nodes Egress after SNAT met Legend Workload AWS service

Subnets and IPs

  • • Place subnets in at least two Availability Zones, pairing a public and a private subnet per AZ
  • • You need pods-per-node × node count IPs, counting ENI secondary IPs
  • • By scale: /24 for small, /20 for medium, /16 for large

DNS settings

  • • Both enableDnsHostnames: true and enableDnsSupport: true are required
  • • Node-to-node traffic, service discovery, and AWS service integration all depend on DNS

Why egress is required

  • • Pulling container images and calling AWS APIs both need an outbound path
  • • Nodes in private subnets use a NAT Gateway; fully private clusters use VPC endpoints