Give several networks a central meeting point — Transit Gateway

Your goal

Attach a VPC to a central transit gateway configuration.

Why this matters

Many separate network links can become hard to manage. A transit gateway provides a central attachment point. You will create a hub and verify one VPC attachment, without claiming end-to-end routing.

Words you will use

A transit gateway is a network hub. An attachment links a network to it. Routes and traffic permissions still determine which connections work.

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 a network hub

Create a VPC and a transit gateway. A transit gateway can act as a central connection point for many networks. This lab focuses on one attachment.

2. Attach the VPC

Create a VPC attachment using your subnet IDs. The attachment joins the VPC to the hub’s configuration. Route tables still control which destinations traffic can reach.

3. Inspect the attachment

Describe the attachment and compare its VPC and gateway IDs with the resources you created. This verifies configuration, not packet delivery between networks.

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.