Keep a second copy in another place — S3 Replication

Your goal

Plan how new files will be copied to a second S3 bucket.

Why this matters

A team wants a copy of new uploads in another region. You will choose replication, include files that already exist, and check whether a copy actually arrived.

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

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

1. Choose the copying plan

New project files should also reach a bucket in a second region. The app should not have to write every file twice itself. Choose the S3 feature to plan.

What fits this requirement?

Set up cross-region replication with the required permissions.

A replication rule selects objects and a destination. Check versioning and permissions for both buckets, including encryption-key access when needed. A rule must be valid before it can copy anything.

The design gives new matching uploads a destination copy.

Source + versioning + role → replication rule → destination

2. Include the older files

The source already held last month’s reports before you enabled live replication. You need those reports in the second bucket too. Choose the missing step.

How should you handle existing objects?

Plan S3 Batch Replication for the older objects.

Live replication handles matching new activity after setup. Existing objects need an appropriate separate plan such as Batch Replication. Check its scope and permissions before starting the job.

The plan covers old reports as well as future uploads.

Existing objects → reviewed Batch Replication job

3. Verify the copy

An upload succeeded in the source, but the team has not checked the destination. Someone declares the second copy ready. Choose the evidence needed first.

What should you inspect?

Replication status, errors, and the destination object.

Replication is asynchronous, so source success does not prove the destination is ready. Monitor failures and verify the copied data. Replication also does not replace every backup or recovery need.

The team checks the second copy before relying on it.

Source success → replication status → destination verification

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.