Hands-on emulator lab · 6–10 min
Give old files a cleanup plan — S3 Lifecycle
Save an expiration rule and inspect when it will apply.
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 expiration rule and inspect when it will apply.
Why this matters
Temporary files can pile up long after they are useful. An expiration rule gives selected files a cleanup schedule. You will choose its lifetime and inspect the saved rule without pretending time has passed.
Words you will use
A lifecycle rule acts on files as they age. A transition changes storage class. Expiration schedules deletion.
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. Set a file lifetime
Enter the number of days for the practice rule. Save it, then inspect its status and expiration period. This lab checks the rule; it does not fast-forward time or claim a file already expired.
Days before expiration: Choose 1–365 days. Only files with the practice/ prefix match this rule. Suggested practice value: 30.
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.