A VPC is your private network in a region. A typical production layout spans 2–3 AZs: Component Role Public subnets load balancers, NAT gateways; route 0.0.0.0/0 → Internet Gateway Private subnets app servers, containers, Lambda (in VPC); outbound via NAT gateway Isolated subnets databases; no internet route at all Security groups stateful, instance-level allow rules (reference other SGs!) Network ACLs stateless subnet-level rules (rarely needed) VPC endpoints private access to S3/DynamoDB (gateway) and other services (interface/PrivateLink) — saves NAT cost Peering / Transit Gateway connect VPCs and on-prem networks Plan CIDR ranges up front (e.g. /16 per VPC, non-overlapping across accounts), and turn on VPC Flow Logs for troubleshooting and security.