Topic lessonTopic: Connecting VPCs and investigating traffic
VPC peering design: routes in both directions and non-transitive connections
An active peering connection does not establish a return path. Trace two VPCs in both directions and explain why a third VPC cannot transit a peer.
Trace two VPCs in both directions and explain why a third VPC cannot transit a peer.
This fictional design assumes familiarity with CIDR and route tables.
Read routes to the peer CIDR on both sides
VPC peering connects two VPCs directly. Accepting peering and routing each participating subnet are separate requirements.
- Worker A → A routeFind the peer CIDR
- A route → Worker BReach the destination
- Worker B → B return routeCheck the return path
- Worker A
- 10.10.0.0/16
- A route
- 10.20.0.0/16 via peer
- Worker B
- 10.20.0.0/16
- B return route
- 10.10.0.0/16 via peer
Only the outward route exists
| Observation | State | Decision |
|---|---|---|
| A to B | Route selects the peer | Outward route exists |
| B to A | No route configured | Reply cannot use the peer |
| C to A | Assumed to transit B | Peering connections are non-transitive |
| Another VPC overlaps A | Same CIDR range | Does not meet peering requirements |
Active describes the connection object. Routes, traffic controls and application responses need separate evidence.
Review the design in order
Find the return path. Use the tables associated with the actual subnets on both sides and check route destinations against the peer CIDR.
Check transit requirements. If C needs A, review a different connection design. Compare Transit Gateway if several networks need shared services.
Keep paired observations. Record the source, destination, port and application outcome for both request and reply.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Identify the VPCs and associated tables.
- Trace the two directions separately.
- Check whether any path requires transit.
Check your understanding: Does Active complete connectivity verification?
Check routes in both directions, traffic controls and reply evidence.
Connection state is one prerequisite.
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.
- How VPC peering connections workChecked:
Scope and conditionsRoutes in both directions, non-transitivity and the CIDR overlap restriction.
Used in this lessonRead routes to the peer CIDR on both sides Only the outward route exists Review the design in order