How it works

Amazon DocumentDB Global Clusters uses storage-based fast replication across regions with latencies less than one second, using dedicated infrastructure with no impact to your workload’s performance. In the unlikely event of a regional degradation or outage, one of the secondary regions can be promoted to full read/write capabilities in less than one minute. You can have up to five secondary regions with Global Clusters, and each secondary region can have up-to 16 replica instances.

Diagram showing how Global Clusters work

Benefits

Disaster recovery from region-wide outages

Region-wide outages are uncommon, but if they do occur, Global Clusters allows you to recover in less than 60 seconds. You can promote your secondary cluster to a standalone cluster and recreate a global database in a different region without any data loss.

Global reads with low latency

You can use Global Clusters to replicate data to other regions so that users can read data from secondary clusters in regions that are closest to them. Global Clusters serve reads locally and with low latency from secondary clusters, while using the primary cluster for writes, helping optimize for use cases with a high read to write ratio.

Scalable secondary clusters

You can scale each secondary cluster independently, as the number and type of instances in the primary and secondary clusters don’t need to be the same. You can create secondary clusters with one replica instance and scale up to 16 instances as needed. Scaling instances in Amazon DocumentDB takes less than 10 minutes, regardless of the data volume.

High-speed replication across clusters

Global Clusters uses fast, storage-based physical replication of data from primary to secondary clusters. The compute instances provisioned don’t participate in replication, which frees them up for serving application requests.

Get started

Get started by converting adding regions to existing Amazon DocumentDB clusters, or by creating a new Amazon DocumentDB Global Cluster using the AWS Console or the AWS CLI.