Cross-account S3 replication, set up in a form

Cross-account replication in AWS is the right answer and a bad afternoon: a replication role, a bucket policy on the far side, versioning on both ends, a rule, and a way to know when it silently stops. Most teams set it up once, for one bucket, and never again.

> Measured from the product, September 2026: 240M+ objects indexed, 50 TB under management, across Amazon S3, Cloudflare R2, Google Cloud Storage and customers' own servers.

• •Mirror a bucket into another account or region from the backup form: BucketPilot writes the replication rule, checks versioning at both ends and keeps it on — a mirror without versioning is not a mirror — and if the replication role is missing, tells you exactly what to grant instead of failing quietly.
• •Or copy on a schedule when replication is not available — a different cloud, or a destination you do not control — with the same incremental job that runs backups.
• •Know when it stops. Mirror health is checked on a schedule and shown on the bucket; the moment a rule is disabled, deleted or its role revoked you get a notification, and another when it works again.
• •Copy across regions and accounts on demand for a one-off: choose the two buckets, press run.

1. 1.Connect both AWS accounts (or one account, two regions) under Credentials.
2. 2.Backups & Migrations → Create, source bucket, destination bucket, and choose Mirror. If the destination is new, create it in the form — it is made with versioning on.
3. 3.Confirm. Replication starts on the next object written; existing objects can be copied by a first backup run.

Mirrors are on the Pro plan and above.