Keep a second copy in another place — S3 and Replication rules

Your goal

Configure a second bucket as a replication destination and inspect the rule.

Why this matters

A second destination can be part of a data-copying plan. The source, destination, and versioning settings must agree. You will configure that relationship and distinguish a saved rule from a completed copy.

Words you will use

Replication copies objects between buckets. A source sends the files; a destination receives them. Asynchronous means the copy can arrive later than the original write.

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 two versioned buckets

Create source and destination buckets, then enable versioning on both. Replication settings refer to these two resources, so their returned names matter.

2. Save the destination rule

Create the practice role and save a replication rule pointing at the second bucket. This lab verifies the configuration; it does not claim the emulator copied objects in the background.

3. Inspect the stored destination

Read the source bucket’s replication settings. Confirm the destination ARN names your second bucket and that the rule is enabled. A saved rule and a completed copy are different results.

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.