Amazon Web Services (AWS) VPC Subnetting
VPC Subnetting Design & Sizing Reference Guide
Amazon Web Services (AWS) VPC
10.0.0.0/16
AWS VPC recommends using the 10.0.0.0/16 address space. Divide the VPC into public subnets (routing via Internet Gateway), private subnets (routing via NAT Gateway), and isolated database subnets (no outbound routes).
Public Subnets: /24 (251 usable hosts per subnet). Private Subnets: /20 (4091 usable hosts per subnet) to allow scaling of application containers. Database Subnets: /24 or /27.
VPC Networking Sizing Principles
Virtual Private Clouds (VPC) form the isolation layer of cloud infrastructure. Proper planning of CIDR sizing prevents address space overlap, ensuring seamless hybrid connections to on-premises datacenters via VPN or dedicated trunks. Sizing application subnets correctly avoids resource exhaustion during high autoscaling demands.
How to configure this cloud VPC subnetwork
1. Create VPC
Create an AWS VPC with IPv4 CIDR block 10.0.0.0/16.
2. Create Subnets
Create public subnet at 10.0.1.0/24 and private subnet at 10.0.16.0/20 across Availability Zones.
3. Configure Route Tables
Attach an Internet Gateway to the public route table and route 0.0.0.0/0 to it. Route private subnet 0.0.0.0/0 traffic to a NAT Gateway.