Transit Gateway Route Tables
What you'll learn: How transit gateway route tables direct traffic between the multiple VPCs, VPNs, and networks connected to your transit gateway.
The Traffic Director's Rulebook
Remember from the previous lesson that a transit gateway acts like a central hub connecting multiple networks. But how does it know where to send traffic? That's where transit gateway route tables come in—they're like the routing rulebook that determines which attachment (VPC, VPN, etc.) receives which traffic.
How They Work
A transit gateway route table contains routes that specify:
- Destination CIDR blocks: Where traffic is headed (like
10.1.0.0/16) - Target attachment: Which connected network should receive that traffic
When a packet arrives at the transit gateway from one attachment, the transit gateway checks its route table to decide which attachment should receive it next.
Multiple Route Tables for Isolation
Here's the powerful part: you can create multiple route tables within a single transit gateway. Each attachment (VPC, VPN connection) can be associated with a different route table. This lets you control network segmentation and isolation.
Example scenario: You might have a "production" route table that only routes between production VPCs, and a separate "shared-services" route table that allows access to common resources like DNS or monitoring systems.
The Analogy
Think of a transit gateway as a train station with multiple platforms (attachments). Each platform has its own departure board (route table) showing which trains (packets) go to which destinations. Different platforms can have different departure boards, controlling which connections they can reach.
Key Takeaway: Transit gateway route tables control which attachments can communicate with each other, enabling both connectivity and network isolation through routing policies.