Route Tables — Complete Guide
Route Tables — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of AWS Cloud Tutorial on Toolliyo Academy.
On this page
AWS Cloud Tutorial · Lesson 13 of 100
Route Tables
Core services → Projects
Core services · 1 — AWS basics · ~6 min · AWS — Networking & Security
What is this?
Route tables define where traffic goes: local VPC, internet gateway, NAT gateway, VPC peering, or Transit Gateway.
Why should you care?
AwsVerse separates route tables so private app tiers cannot be reached from the internet.
See it live — copy this example
Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).
aws ec2 create-route \
--route-table-id rtb-private1 \
--destination-cidr-block 0.0.0.0/0 \
--nat-gateway-id nat-0def456What happened?
- Adds default route from a private subnet table to NAT Gateway.
- Outbound internet works; inbound from IGW does not.
Practice next
- Create public RT: 0.0.0.0/0 → igw-xxx, local → vpc.
- Create private RT: 0.0.0.0/0 → nat-xxx.
- Associate each subnet with exactly one route table.
- Add route 10.30.0.0/16 via VPC peering connection.
- Use aws ec2 describe-route-tables to audit.
Remember
Route table = traffic director. Public: IGW; private: NAT. One subnet → one RT association.
AwsVerse egress control
Apps need updates but no inbound SSH from internet.
Outcome: Private RT via NAT satisfies patch egress without public IPs.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
