Prepare the gateways for a VPN — Site-to-Site VPN

Your goal

Prepare a VPN customer gateway and attach the AWS-side gateway to a VPC.

Why this matters

A planned office-to-cloud connection needs gateway records and a VPC attachment. You will prepare those pieces. The installed emulator does not create the VPN tunnel itself.

Words you will use

A VPN tunnel encrypts network traffic. The customer gateway represents your side of the connection. AWS provides the other end.

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 both gateway records

Create a VPC, a customer gateway with a reserved documentation address, and a virtual private gateway. They describe the network and the two ends of a future connection.

2. Attach the AWS-side gateway

Attach the virtual private gateway to your VPC. The emulator does not implement creating the VPN connection itself. This exercise prepares and verifies the gateway attachment without claiming to create a tunnel.

3. Inspect the gateway attachment

Describe the gateway and find your VPC ID in its attachments. Real site-to-site VPN setup still needs a VPN connection, customer equipment, routes, and tunnel configuration.

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.