This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
3.2 Read-replicas in Amazon RDS from on-premises databases
Requirements addressed:
-
REQ1 (data residency)
-
REQ4 (availability and durability)
-
Customer-REQ1 (reliable connectivity)
AWS services –
Amazon RDS

Read-replicas in Amazon RDS
Read-replicas in Amazon RDS
You can use AWS Database Migration Service
REQ1 is fulfilled by performing collection of personal data (such as writes, changes, and updates) in the local primary database.
REQ4 is fulfilled by AWS Database Migration Service, which continuously copying data from the local database to Amazon RDS (2A & 2B) in the AWS Region, and (optionally) another copy to an Amazon S3 (3A & 3B) bucket for backup purposes. (Refer to Using Amazon S3 as a target for AWS Database Migration Service). Continuous data replication allows both homogeneous and heterogeneous data replications for supported database engines. For a full list supported database engines, refer to Sources for AWS DMS and Targets for AWS DMS. Write, change, and update operations are restricted for other services (except AWS DMS) on Amazon RDS by allowing only read workloads using appropriate permissions. You can set up Amazon RDS to be the target replica by using native replication (4A & 4B) mechanisms provided by the local database engine.
Customer-REQ1 – AWS DMS or native replication flows an be performed over AWS Direct Connect and/or AWS Site-to-Site VPN. For more details, refer to 1:1: Hybrid network connectivity from a data center to the AWS Cloud.
For more details about Oracle Disaster Recovery using DMS, refer
to
Disaster
recovery on Amazon RDS for Oracle using AWS DMS