Hands-on emulator lab · 6–10 min
Give a server a lasting disk — EBS and EC2
Create a disk volume, label its purpose, and inspect its stored settings.
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
Create a disk volume, label its purpose, and inspect its stored settings.
Why this matters
A disk’s ID, size, zone, and purpose tell a team what it is for. You will create a volume record, label it, and retrieve that same volume. This is resource configuration, not a mounted file system.
Words you will use
EBS is block storage used like a disk. A volume is one disk. A snapshot is a saved point-in-time copy used to create another volume.
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 practice disk
Create a small gp3 EBS volume in one Availability Zone. This creates a disk resource in the emulator, not a disk mounted in your browser or on this host.
2. Label what the disk is for
Save a Purpose tag with your practice label. Tags help identify resources but do not contain file data or replace access controls.
Practice label: This label is saved in the emulator. Use 1–80 characters. Suggested practice value: moonbase.
3. Inspect the same volume
Read this volume by ID. Check its size, zone, state, and Purpose tag. The lab verifies the tag on the resource you created rather than accepting a remembered label.
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.