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

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.

What you will learn

Trace two VPCs in both directions and explain why a third VPC cannot transit a peer.

Prerequisite

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.

Paths for the request and reply
Paths for the request and reply1: Worker A — Find the peer CIDR — A route. 2: A route — Reach the destination — Worker B. 3: Worker B — Check the return path — B return route123Worker AA routeWorker BB return routePaths for the request and reply1: Worker A — Find the peer CIDR — A route. 2: A route — Reach the destination — Worker B. 3: Worker B — Check the return path — B return route123Worker AA routeWorker BB return route
  1. Worker A → A routeFind the peer CIDR
  2. A route → Worker BReach the destination
  3. 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

A–B and B–C have active peerings and non-overlapping CIDRs.
ObservationStateDecision
A to BRoute selects the peerOutward route exists
B to ANo route configuredReply cannot use the peer
C to AAssumed to transit BPeering connections are non-transitive
Another VPC overlaps ASame CIDR rangeDoes 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.

B has no return route. What is the next check?
Read the answer and reason

Answer: Check B’s table for A’s CIDR · Examine the actual route table used by B.

Can C reach A through B’s two peering connections?
Read the answer and reason

Answer: A different route design is needed · VPC peering is non-transitive.

What if a candidate peer has A’s address range?
Read the answer and reason

Answer: Revisit addressing or connectivity design · Overlapping CIDRs violate the peering constraint.

Check, then explain in your own words

  1. Identify the VPCs and associated tables.
  2. Trace the two directions separately.
  3. 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.