18-Sep-2026 — Copy site files safely between AWS accounts ref #231

Commit 7bf0084

What's new

Environment Migration can now copy a group's live S3 bucket into an AWS account you type in, alongside restoring MongoDB to a cluster you type in. After a successful copy, Rotate Credentials points the environment at the new database and AWS keys. That is the move Head office need: a disposable Atlas database and a disposable AWS account, then Validate Plan, Restore, Rotate.

At a glance

• Destination bucket, region, access key and secret appear on the form when S3 copy is switched on
• The destination bucket is created if it does not exist, with the same public access and CORS setup a new site gets
• Objects keep their access setting, content type and cache headers, so images and files still load after cutover
• An interrupted copy resumes where it stopped, skipping unchanged objects
• Rotate Credentials is a separate typed confirmation, and records the previous keys so a bad rotation can be reversed

Where to find it

Admin → Platform → Environment management → Environment Migration. The same destination settings are available on the command line.

How to try it out

1. Choose the environment and a completed backup to restore.
2. Enter the destination MongoDB cluster, switch on S3 copy and enter the destination AWS details.
3. Click Validate Plan to list what would be copied without writing anything.
4. Run the restore and copy.
5. Use Rotate Credentials to point the site at the new database and AWS keys.

How it behaves

Rotate Credentials refuses to point the site at an AWS account other than the one just copied to. Unchanged objects are skipped by size and checksum rather than copied again.