Module 1 of 6 β€’ Foundation of AWS Networking

VPCs, Subnets, Route Tables & The Internet Gateway

Why can a customer reach your web server in a Public Subnet, while your database in a Private Subnet stays completely invisible to the outside world? Toggle the routing switches on the right and fire test packets to see the three things required for internet connectivity.

πŸ—ΊοΈ
The Big Secret: AWS doesn't have a magic button that makes a subnet "Public." Every subnet starts out completely private! A room (Subnet) only becomes Public when you: (1) build a front gate on your campus (Internet Gateway), (2) put a sign on the hallway map (Route Table) pointing outside traffic (0.0.0.0/0) to that gate, and (3) give the server inside a public street address (Public IP).
Next: Module 2 (ENIs & NAT) β†’ ← Back to Big Picture Hub
Interactive VPC & Route Table Simulator
🌍 INTERNET πŸ§‘πŸ½β€πŸ’» Customer 198.51.100.42 Outside AWS 🏒 VPC (10.0.0.0/16) β€” 65,536 Total Private IP Addresses Region: us-east-1 β€’ Isolated Virtual Network πŸšͺ IGW igw-01 ATTACHED 🧭 VPC Router 10.0.x.1 in each subnet 10.0.0.0/16 β†’ local Consults Route Tables 🌀️ Subnet A: 10.0.1.0/24 (AZ: us-east-1a) β€” PUBLIC 251 Usable IPs (5 Reserved by AWS: .0, .1, .2, .3, .255) πŸ“‹ Route Table A (rtb-pub) 10.0.0.0/16 β†’ local 0.0.0.0/0 β†’ igw-01 βœ“ Has route to Internet Gateway πŸ–₯️ Web Server EC2 Priv IP: 10.0.1.15 Pub IP: 54.210.10.5 πŸ›‘οΈ SG: Allow TCP 443 πŸ”’ Subnet B: 10.0.2.0/24 (AZ: us-east-1b) β€” PRIVATE Isolated from direct inbound Internet traffic πŸ“‹ Route Table B (rtb-priv) 10.0.0.0/16 β†’ local (No 0.0.0.0/0 IGW route) πŸ”’ Cannot reach or be reached by IGW πŸ—„οΈ Production DB Priv IP: 10.0.2.99 No Public IP Assigned πŸ›‘οΈ SG: Allow 5432 from Web
local route = free internal VPC traffic 0.0.0.0/0 β†’ igw-01 = makes a subnet Public
Flip the switches on the right and click a Test button above!