Elevate Your Infrastructure : Harnessing Cross-Region Replication for Global Efficiency

Cross-region replication in Amazon Relational Database Service (Amazon RDS) allows us to create a read-only database instance in a different AWS region than your primary database instance. RDS Cross-Region Read Replicas Process RDS creates an automated DB snapshot of the source DB instance in the source AWS Region. RDS begins a cross-Region snapshot copy for the initial data transfer. RDS then uses the copied DB snapshot for the initial data load on the read replica.

Disaster recovery : If your primary region experiences a disruption, you can promote a replica to a master to keep your business running.

Data proximity : You can place replicas closer to your application users to reduce read latency.

Database migration : You can quickly migrate your database to a different AWS region.

Read workload scaling : Cross-region replication allows you to scale out read workloads over a farm of up to five read replicas.

Read workload offloading : You can offload read workload from your primary database instance.

Amazon RDS uses the replication functionality integrated into the MariaDB, MySQL, Oracle, PostgreSQL & Microsoft SQL Server database engines to create a special type of DB instance called a Read Replica from a source DB instance. Cross-region replication is a feature that automatically replicates data across regions to provide disaster recovery protection.

Step 1 : On the RDS database hit to create database choose a database engine.

Step 2 : Then choose a template according to your potentials. And choose single DB instance, give a identifier to your database and fill the credentials as asked.

Step 3 : Then come on Instance configuration choose Burstable classes(Includes t classes)

Step 4 : On storage whatever allocated storage given by default go as along with it.

Step 5 : On connectivity give access to the public choose a security group.

Step 6 : Leave everything as default then hit the create database button.

Step 7 : Here we can see our database is created successfully.

Step 8 : Let’s try to connect with database endpoint.

Step 9 : Here we connected successfully to the databases. Here we will create a database with terminal.

Step 10 : After all that things we remember thta we’ve to do one important thing to create that one is Read-Replica.

Step 11 : Creating the Read Replica within the region where the database created and we want to create this read replica on another region. Here Everything most probably remain same and on AWS Region we have to choose our destination region. In Our’s end we chose Ohio(US-EAST).

Step 12 : On AZ we can go with single db instance for practice purpose.

Step 13 : Leave everything as default and hit the button Create read replica.

Step 14 : Here our primary database available is in N.Virginia.

Step 15 : From here we’ll go to the Ohio.

Step 16 : Hola !! Here is our Read replica which we have created on N.Virginia.

Step 17 : Not only read replica even its all about Subnet-Groups we’ve created a subnet groups from N.Virginia the Subnets groups also are here.

Stepp 18 : Here We will try to connect with read replica’s endpoints and we’ll try to see that the database we’ve created the database through terminal on mysql -h are they’ll visible here.

Step 19 : Edit the Security groups attached with our primary database and add MYSQL /AURORA.

Step 20 : Here we’ve connected with our mysql host from Ohio Region and when se didi show databases. And we can see that the databse we have cretaed through terminal on which was created on N.Virginia Region.

Step 21 : Here after our practice we’ve to remove our instance or AWS resources.

thank Yu !!