Hands-on emulator lab · 6–10 min
Record the settings you want to watch — AWS Config and Versioning rules
Save an AWS Config rule for checking whether S3 versioning is enabled.
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
Save an AWS Config rule for checking whether S3 versioning is enabled.
Why this matters
A compliance rule must say which resources and setting it checks. You will configure an S3 recorder scope and a versioning rule. A rule definition is different from a completed evaluation.
Words you will use
A recorder collects resource configuration history. A resource type is a class such as EC2 instances. A recording group defines what should be watched.
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 configuration recorder
Create a recorder configuration using a service role. A recorder describes which resource configurations to track. This lab does not start continuous recording or claim to have collected real account history.
2. Create the versioning rule
Save an AWS-managed rule named S3_BUCKET_VERSIONING_ENABLED and scope it to S3 buckets. A rule definition says what should be checked; an evaluation result says what was actually found.
3. Read the rule definition
Describe the rule and inspect its source identifier and scope. This lab verifies the rule configuration, not a completed compliance evaluation.
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.