Request a link between private networks — VPC and VPC peering

Your goal

Create a peering request between two separate private networks.

Why this matters

A direct private-network link begins with two address ranges and a peering request. You will create that request and inspect both ends. Acceptance is outside the installed emulator’s supported operations.

Words you will use

A CIDR range is a block of network addresses. Peering links two VPCs. A route tells traffic where to go. Transitive routing means reaching a third network through an intermediate one.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create different address ranges

Create two VPCs with non-overlapping address ranges. Distinct ranges let each network identify the other’s addresses. These are isolated configuration records.

2. Request a peering connection

Create a request from the first VPC to the second. This emulator supports the request but does not implement acceptance. We stop at a real saved request instead of pretending an active connection exists.

3. Inspect both ends and the status

Describe the request and compare its requester and accepter VPC IDs. Read its actual status. In AWS, acceptance, routes, and security rules are further steps before traffic can pass.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.