Cloud concept · Updated

Data Replication - Data replication is the process of maintaining copies of the same data on multiple storage systems or locations and propagating changes between them.

In short

Replication helps systems preserve data and continue operating when hardware, servers, or entire locations fail. Its effectiveness depends on where replicas are placed, how changes are acknowledged and synchronized, and whether applications can switch to a usable replica.

Cloud Concepts Hub →

6 key aspects of Data Replication

Effective replication combines appropriate replica placement, propagation semantics, consistency, failover procedures, and independent recovery protection.

01
Failure-domain separation

Place replicas across independent failure domains that match the required protection level. Multiple copies within one Availability Zone do not provide the same protection as copies distributed across zones or Regions.

02
Synchronous and asynchronous propagation

Synchronous replication requires specified replica acknowledgments before a write succeeds, adding latency and communication dependencies. Asynchronous replication reduces that dependency but permits lag and potential loss of unreplicated writes.

03
Consistency and read behavior

A replica can contain older data than the writer, depending on the replication and consistency model. Route freshness-sensitive reads appropriately and do not assume that every replica immediately reflects a successful write.

04
Recovery objectives and failover

Use RPO to determine acceptable data loss and RTO to determine acceptable recovery time. Confirm whether failover is automatic, whether a replica needs promotion, and how applications reconnect.

05
Durability versus availability

Replication can improve both data retention and service continuity, but these are separate outcomes. A stored copy may survive a failure while remaining temporarily inaccessible or unavailable for writes.

06
Independent recovery protection

Maintain backups or version history because replication can propagate unwanted changes. Monitor replication health and test recovery rather than treating the existence of a replica as proof of recoverability.

Cloud services for Data Replication

Select replication separately for each application data layer: S3 for objects, EBS for instance-attached block storage, EFS for shared files, and RDS, Aurora, or DynamoDB for database data. Their default failure boundaries and failover behavior differ, so one replicated component does not make the whole application resilient. A multi-zone application might combine regional object storage with a Multi-AZ database, while a regional recovery plan also needs suitable cross-Region copies, application infrastructure, routing, and encryption-key access. Retain backups and test recovery across all dependent layers.

Amazon S3Amazon S3

S3 Standard stores objects redundantly across multiple Availability Zones, while S3 One Zone-IA uses a single Availability Zone. S3 Replication provides asynchronous copying between buckets in the same or different Regions; existing objects require a separate mechanism such as S3 Batch Replication.

Amazon RDSAmazon RDS

RDS Multi-AZ DB instance deployments synchronously replicate to a standby in another Availability Zone for high availability; that standby does not serve reads. Read replicas typically use asynchronous replication for read scaling and potential promotion, while Multi-AZ DB clusters have a different architecture with readable instances.

Amazon AuroraAmazon Aurora

Aurora replicates its cluster storage across three Availability Zones, separating storage durability from database-instance availability. Aurora Replicas provide read capacity and failover targets, while Aurora Global Database uses asynchronous cross-Region storage replication for geographic reads and disaster recovery.

Amazon DynamoDBAmazon DynamoDB

DynamoDB replicates table data across multiple Availability Zones within a Region. Global tables extend replication across Regions, with multi-Region eventual consistency and multi-Region strong consistency options that have different latency, topology, and regional-availability constraints.

Data Replication exam questions

Real practice exam questions on Data Replication, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAA-C03

A company stores customer uploads in an Amazon S3 bucket in its primary AWS Region. An existing replication rule copies all new objects to a bucket in a recovery Region. Both buckets have versioning enabled. The application can switch to the recovery bucket during a primary Region outage, and every upload uses a unique object key. Existing objects are never modified.

After the primary Region recovers, objects uploaded to the recovery bucket during the outage must automatically be copied to the primary bucket. The company does not want to maintain custom copying code.

Which change should a solutions architect make before an outage to meet this requirement?

Show answerCORRECT ANSWER

Add a replication rule on the recovery bucket that copies all new objects to the primary bucket, with the required IAM permissions.

The additional rule establishes replication in the reverse direction. Objects uploaded to the recovery bucket during failover become source objects for this rule and are asynchronously replicated to the primary bucket when the destination is available. Unique keys and immutable objects avoid conflicting updates.

SAP-C03

A media company stores 300 TB of existing objects in a versioned Amazon S3 bucket in its primary AWS Region. An application reads objects and creates new objects by using unique keys. The company has deployed a standby application and an empty, versioned S3 bucket in a second Region.

The company requires a disaster recovery design with the following characteristics:
• All existing objects and future objects must be protected in the second Region before the design is accepted for production.
• During normal operation, all application object requests must go to the designated primary Region.
• Operators must be able to redirect object requests to the recovery Region within minutes without changing application configuration or DNS records during an incident.
• The application must use one stable S3 endpoint and continue creating objects after failover. Those objects must be available in the original Region before a subsequent failback.

The application supports the signing requirements for a global S3 endpoint. The business accepts the possibility of losing recent objects that have not completed asynchronous replication during an unexpected Regional failure. Operators can wait for replication to complete before a planned failback.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Configure bidirectional S3 Cross-Region Replication between the buckets. Use S3 Batch Replication to replicate the existing objects, and verify completion before production acceptance. Create an S3 Multi-Region Access Point with an active-passive routing configuration. Use its failover controls to switch the active bucket during recovery, and verify that recovery-Region writes have replicated back before failback.

Bidirectional Cross-Region Replication protects new objects created in either Region, including objects created while the recovery Region is active. S3 Batch Replication handles objects that existed before the replication rules were configured. An S3 Multi-Region Access Point provides a stable global endpoint, and its active-passive failover controls let operators redirect requests without changing application configuration or DNS records. Verifying reverse replication before failback protects objects created during recovery.

Practice Data Replication in a full exam

Questions on Data Replication in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Data Replication

3 min read

Data replication maintains multiple copies of data and propagates changes between them. Cloud storage and database services use replication to tolerate infrastructure failures, support recovery, and sometimes distribute read traffic. Replication can operate at the block, file, object, or database-record level. The key architectural question is not simply whether copies exist, but which failures those copies can survive and how applications access them afterward.

Replica placement determines the scope of protection. Copies on separate devices can protect against a disk failure, but copies within one Availability Zone do not provide protection against losing that entire zone. Replication across Availability Zones supports resilience to a zone failure. Cross-Region replication can support regional disaster recovery, geographic access, or regulatory requirements, but usually introduces greater network latency, transfer costs, and operational complexity.

Synchronous replication waits for the required replica acknowledgments before reporting a write as successful. Depending on the replication protocol and failure scenario, this can prevent the loss of acknowledged writes when a primary fails. The trade-off is additional write latency and possible write unavailability when required replicas cannot communicate. Synchronous replication does not necessarily mean that every copy has received the write; some systems require acknowledgment from a quorum.

Asynchronous replication acknowledges writes before all replicas receive them. It can reduce foreground write latency and is commonly used across Regions or for read replicas. However, a replica can lag behind the source. For example, a customer who updates an address and immediately reads from a lagging replica might see the old address. If the source fails before its latest writes are replicated, promoting that replica can lose those writes.

Recovery point objective, or RPO, describes the acceptable amount of data loss measured in time. Recovery time objective, or RTO, describes how quickly service must be restored. Replication lag influences achievable RPO, while failure detection, replica promotion, application reconnection, and routing influence RTO. A replicated copy alone does not guarantee automatic failover or uninterrupted service. Applications still need connection retries, appropriate timeouts, and a tested recovery process.

Durability and availability are different characteristics. Durability concerns retaining data without loss; availability concerns being able to access the service when needed. A highly durable storage system can temporarily be unavailable. Similarly, a readable replica might improve availability without containing the latest writes. Read replicas may increase read capacity, but they generally do not increase the write capacity of a single-writer database.

Replication is not a substitute for backup. Accidental updates, corrupted application writes, or malicious changes can propagate to replicas. Versioning, point-in-time recovery, retained backups, and immutable copies provide recovery options that live replicas alone do not. For example, replicate an order database across zones for infrastructure resilience while retaining backups to recover from an accidental table deletion.

Evaluate the replication behavior of each storage class and deployment option rather than assuming an entire service behaves uniformly. A block volume replicated within one zone remains tied to that zone's failure boundary, whereas a multi-zone storage service provides a different level of protection. Monitor lag and replication failures, verify permissions and encryption-key access at recovery locations, and test failover under realistic workloads. For architecture questions, match the required failure scope, data-loss tolerance, recovery time, consistency, and cost to the actual replication configuration.

Learn Data Replication in lessons

4 short lessons on Data Replication in 2 certification courses.

Open the lessons