Recover a file from a separate copy — S3 and File recovery

Your goal

Keep a second copy, remove the original, and restore the file from that copy.

Why this matters

A second copy is useful only if you can recover its contents. You will verify a copy, delete the original practice file, and restore it. Reading the restored text makes recovery an observed result.

Words you will use

A backup copy keeps data separately from the original. A restore puts usable data back after a loss. Checking the recovered contents tells you whether this small recovery worked.

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 file and a separate backup bucket

Create a source bucket and a second bucket for a backup copy. Save your message as lesson.txt in the source. This small exercise gives you known data to recover.

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

2. Copy the file, then remove the original

Copy lesson.txt into the backup bucket and read the copy to check its contents. Only after that check, delete the source object. This deliberately creates a recoverable loss inside your private lab.

3. Restore and compare the recovered file

Copy the backup object back to the source bucket, then retrieve it and compare its contents. This is an actual local recovery drill. It does not simulate a Region outage or provide cross-account backup isolation.

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.