Topic lessonTopic: Connecting VPCs and investigating traffic
Transit Gateway routing: associations and propagation across environments
An attachment alone does not determine which destinations it can reach. Follow the ingress attachment to its route table and confirm destination routes.
Follow the ingress attachment to its route table and confirm destination routes.
This is a fictional single-Region configuration. No real settings are changed.
Start with the ingress attachment
Transit Gateway checks the associated table to select the next hop. Propagation adds routes from an attachment to a selected table.
- Development VPC → AssociationIdentify ingress
- Association → Destination lookupRead the associated table
- Destination lookup → Next hopIdentify the next hop
- Development VPC
- Attachment D
- Association
- Development table
- Destination lookup
- Route for shared CIDR
- Next hop
- Shared attachment
Allow shared service traffic while separating production
| Direction | Table and route | Decision |
|---|---|---|
| Development → shared | Development table contains shared CIDR | TGW can forward to shared |
| Development → production | Development table has no production CIDR | No next hop in this table |
| Shared → development | Shared table lacks development CIDR | Return route is missing |
| Production → shared | Production table contains shared CIDR | Outward route established only |
Association and propagation are independent. A route from development to shared says nothing about the return table.
Trace the paths without dropping segmentation
Identify the ingress lookup. Record the source attachment, its association, matching route and next hop.
Invert the route for the reply. The reply enters through the shared attachment. Use that association and look up the development CIDR.
Keep sharing intentional. Check needed routes and permissions individually. Propagating production into every table can undermine the separation.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Identify the ingress attachment.
- Match the associated table and destination entry.
- Check the opposite direction independently.
Check your understanding: Does enabling propagation also change the association?
Verify which table is read and which receives routes separately.
Association and propagation perform separate jobs.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsAn association selects the lookup table; propagation supplies routes.
Used in this lessonStart with the ingress attachment Allow shared service traffic while separating production Trace the paths without dropping segmentation