Amazon S3 Cross-Region Replication (CRR)

With S3 Cross-Region Replication (CRR), you can replicate objects (and their respective metadata and object tags) into other AWS Regions for reduced latency, compliance, security, disaster recovery, and other use cases. S3 CRR is configured to a source S3 bucket and replicates objects into a destination bucket in another AWS Region.

Amazon S3 CRR automatically replicates data between buckets across different AWS Regions. With CRR, you can set up replication at a bucket level, a shared prefix level, or an object level using S3 object tags. You can use CRR to provide lower-latency data access in different geographic regions. CRR can also help if you have a compliance requirement to store copies of data hundreds of miles apart. You can use CRR to change account ownership for the replicated objects to protect data from accidental deletion. To learn more about CRR, visit the replication developer guide.

Use cases

Compliance — Amazon S3 stores your data across multiple geographically distant Availability Zones by default, but compliance requirements might dictate that you store data at even greater distances. CRR enables you to replicate data between distant AWS Regions to satisfy these requirements.

Latency performance — You can minimize latency if your customers or end-users are in two geographic locations, you can minimize latency in accessing objects by maintaining object copies in AWS Regions that are geographically closer to your users.

Regional efficiency — If you have compute clusters in two different AWS Regions that analyze the same set of objects, you might choose to maintain object copies in those Regions.

Amazon S3: Cross-Region Replication & Versioning (3:34)

Amazon S3 Same-Region Replication (SRR)

Amazon S3 SRR is an S3 feature that automatically replicates data between buckets within the same AWS Region. With SRR, you can set up replication at a bucket level, a shared prefix level, or an object level using S3 object tags. You can use SRR to make a second copy of your data in the same AWS Region. SRR helps you address data sovereignty and compliance requirements by keeping a copy of your data in a separate AWS account in the same region as the original. You can use SRR to change account ownership for the replicated objects to protect data from accidental deletion. You can also use SRR to easily aggregate logs from different S3 buckets for in-region processing, or to configure live replication between test and development environment. 

Use cases

Aggregate logs into a single bucket — If you store logs in multiple buckets or across multiple accounts, you can easily replicate logs into a single, in-Region bucket. This allows for simpler processing of logs in a single location.

Replication between developer and test accounts — If you or your customers have developer and test accounts that use the same data, you can replicate objects between those multiple accounts, while maintaining object metadata, by implementing SRR rules.

Abide by data sovereignty laws — Often customers are required to store data in separate AWS accounts while being barred from letting the data leave a certain Region. Same-Region replication can help you back up critical data when compliance regulations don't allow the data to leave your country.

Amazon Replication Time Control

Amazon S3 replication time control helps you meet compliance "or business requirements" for data replication and provides visibility into Amazon S3 replication activity. Replication time control replicates most objects "that you upload" to Amazon S3 in seconds, and 99.99 percent of those objects within 15 minutes.

S3 Replication Time Control is backed by a Service Level Agreement (SLA) on the replication of 99.9% of objects within 15 minutes during any billing month.

S3 Replication Time Control provides S3 Replication metrics that monitor the total number and size of objects being replicated and when that data was replicated to its destination. S3 Replication Time Control helps you meet compliance or business requirements for predictable replication times, and monitors that replication though Amazon CloudWatch Metrics at the replication policy level. To learn more about S3 Replication Time Control, visit the S3 Replication documentation page or the S3 Replication FAQs.

How S3 Replication Time Control works

DIAGRAM-TEMPLATE

Getting started with S3 Replication

Amazon S3 Replication (CRR and SRR) and S3 Replication Time Control are configured at the S3 bucket level, a shared prefix level, or an object level using S3 object tags. To get started with S3 Replication, please read the S3 Replication FAQs, the Replication web page in the Developer Guide, and for pricing see S3 Replication features pricing.