INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Follow the ingress attachment to its route table and confirm destination routes.

Prerequisite

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.

A development VPC reaches a shared service
A development VPC reaches a shared service1: Development VPC — Identify ingress — Association. 2: Association — Read the associated table — Destination lookup. 3: Destination lookup — Identify the next hop — Next hop123Development VPCAssociationDestination lookupNext hopA development VPC reaches a shared service1: Development VPC — Identify ingress — Association. 2: Association — Read the associated table — Destination lookup. 3: Destination lookup — Identify the next hop — Next hop123Development VPCAssociationDestinationlookupNext hop
  1. Development VPC → AssociationIdentify ingress
  2. Association → Destination lookupRead the associated table
  3. 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

VPC routes already point at the TGW. Development should only reach shared services.
DirectionTable and routeDecision
Development → sharedDevelopment table contains shared CIDRTGW can forward to shared
Development → productionDevelopment table has no production CIDRNo next hop in this table
Shared → developmentShared table lacks development CIDRReturn route is missing
Production → sharedProduction table contains shared CIDROutward 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.

Which TGW table applies to traffic from development?
Read the answer and reason

Answer: Development table · The ingress attachment selects the associated table.

The outward route exists but replies fail. What next?
Read the answer and reason

Answer: Check the shared table for the development CIDR · Replies enter from the shared attachment.

The development table lacks the production CIDR. What is established?
Read the answer and reason

Answer: This TGW table has no next hop for that destination · The evidence applies to this table.

Check, then explain in your own words

  1. Identify the ingress attachment.
  2. Match the associated table and destination entry.
  3. 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.