Reach a service through a private doorway — VPC and S3 gateway endpoints

Your goal

Add an S3 gateway endpoint to a private network configuration.

Why this matters

A private VPC can have a service-specific path to S3 through a gateway endpoint. You will connect an endpoint to a route table and inspect its service and VPC IDs. This is not a network traffic test.

Words you will use

A gateway endpoint gives a VPC a service-specific route to S3. A route table lists network paths. An endpoint ID identifies this saved connection configuration.

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. Prepare a VPC and route table

Create the practice network and a route table. A gateway endpoint adds a service path through route tables. This is a routing configuration exercise, not a connectivity test.

2. Create the S3 endpoint

Add a gateway endpoint for S3 and associate your route table. The request names a specific AWS service and VPC. No public internet gateway is needed for this configuration.

3. Check the service and network

Describe your endpoint by its ID. Confirm that it names S3 and the VPC you created. Policies, route associations, and real traffic require further checks outside this lab.

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.