Hands-on emulator lab · 6–10 min
Build a private neighborhood — VPC and Security groups
Build a private network and turn on its DNS hostname setting.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Build a private network and turn on its DNS hostname setting.
Why this matters
A private network has its own address ranges and DNS settings. You will create a VPC and subnets, enable hostnames, and verify that setting. The exercise does not test packet delivery.
Words you will use
A VPC is your private cloud network. A subnet is one part of it. A route is a traffic path. A security group controls which connections are allowed.
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 your private neighborhood
Create one VPC, two smaller subnet ranges, and a security group. The response shows their IDs. These are network configuration records; this lab does not open a network connection.
2. Enable DNS hostnames
Turn on the setting that lets eligible instances receive DNS hostnames. DNS names are easier to recognize than numeric addresses. This does not give a private instance public internet access.
3. Check the VPC setting
Read enableDnsHostnames from the same VPC. Find the true value in the response. The lab checks that the change belongs to the network you created.
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.