Protect a saved file version — S3 and Object Lock

Your goal

Save an object version with governance retention and inspect its protection.

Why this matters

Some file versions need a retention period to reduce accidental deletion. You will save a practice version with governance retention and inspect that exact version’s record. This is not a compliance test.

Words you will use

Versioning keeps separate copies of a file. Retention protects a version for a period. Object Lock controls deletion of protected versions.

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 bucket for protected versions

Create a bucket with Object Lock enabled and enable versioning. The protection applies to individual versions, so this setup is needed before saving the file.

2. Save a protected practice file

Upload a short message with governance retention lasting one day in emulator time. We use practice data only. Governance mode can be bypassed by suitably authorized callers; it is not the same as compliance mode.

Practice message: Type a short message that you can recognize in the API result. Suggested practice value: Hello from my lab.

3. Inspect this version’s retention

Retrieve the retention record using the exact version ID returned by the upload. Check the mode and date. This lab verifies stored retention metadata, not regulatory compliance or every deletion rule.

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.