Hands-on emulator lab · 6–10 min
Give files an undo button — S3 Versioning
Enable version history and verify the setting stored on your bucket.
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
Enable version history and verify the setting stored on your bucket.
Why this matters
Replacing a file can accidentally hide an earlier copy. Versioning is the bucket setting that makes separate file versions possible. You will enable it and check that S3 saved the change.
Words you will use
An object is a file in S3. Its key is its name. A version ID labels one saved copy of that file.
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 practice bucket
Start by creating a bucket in your private emulator. Its unique name appears in the response. This bucket is the resource you will configure in the next step.
2. Turn on version history
Save the Enabled setting. Versioning allows later writes to keep distinct file versions. In this step you configure the feature; the response in the next step confirms it is enabled.
3. Read the setting back
Ask S3 for the current setting. Compare the returned value with what you submitted. Completion uses this fresh response, so a button click by itself is not enough.
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.