{"id":785,"date":"2021-11-30T11:19:19","date_gmt":"2021-11-30T11:19:19","guid":{"rendered":"https:\/\/www.workfall.com\/learning\/blog\/?p=785"},"modified":"2025-08-20T11:10:45","modified_gmt":"2025-08-20T11:10:45","slug":"how-to-perform-an-amazon-aurora-database-deployment-that-replicates-data-and-spans-across-multiple-aws-regions","status":"publish","type":"post","link":"https:\/\/learning.workfall.com\/learning\/blog\/how-to-perform-an-amazon-aurora-database-deployment-that-replicates-data-and-spans-across-multiple-aws-regions\/","title":{"rendered":"How to perform an Amazon Aurora Database deployment that replicates data and spans across multiple AWS regions?"},"content":{"rendered":"Reading Time: <\/span> 9<\/span> minutes<\/span><\/span>\n

<\/p>\n\n\n\n

Amazon Web Services provides us with the flexibility of managing the data in the databases with ease. The flexibility is thus provided by an AWS Service called Amazon Aurora. An Amazon Aurora cluster contains one or more DB instances and a cluster volume that helps us manage the data for those DB instances. A cluster volume is basically a virtual database storage volume that spreads across various availability zones. Each zone thereby has two copies of the data. There exist two types of database instances that make up a cluster. A primary instance that supports read and write actions and a replica that connects to the same volume but only supports read-only operations. Each cluster can only have up to 15 replicas that span across the three availability zones. If ever the primary database instance becomes unavailable or not in use, Amazon Aurora automatically initiates the process of failing over to an Aurora Replica. In this blog, we will have a look at how we can make use of the Amazon RDS<\/a> flexibilities to deploy an Amazon Aurora Global Database that replicates the data and spans across multiple regions.<\/p>\n\n\n\n

Amazon Aurora – Recap<\/h2>\n\n\n\n
\"Amazon<\/figure>\n\n\n\n

Amazon Aurora<\/a> is a relational database for the cloud that supports MySQL<\/a> and PostgreSQL<\/a> and combines the speed and availability of standard enterprise databases with the simplicity and cost-effectiveness of open-source databases.<\/p>\n\n\n\n

Amazon Aurora databases are up to 5x faster than MySQL databases and 3x faster than PostgreSQL databases. It offers commercial databases security, availability, and reliability at a fraction of the cost. Amazon RDS handles all aspects of Amazon Aurora, including hardware provisioning, database setup, patching, and backups.<\/p>\n\n\n\n

Hands-on<\/strong><\/h2>\n\n\n\n
\"Amazon<\/figure>\n\n\n\n

In this hands-on, we will see how we can perform an Amazon Aurora Database deployment thereby replicating the data across secondary databases in some other AWS region. Navigating to the Amazon RDS dashboard, we will create a new Amazon Aurora database which will consist of the required data to be replicated. We will create an Amazon Aurora cluster instance with the latest version of MySQL support for the Dev\/Test template. While configuring the DB instances, we will be using the memory-optimized instances with the r family series. Blocking the public access for the Database instance, we will create a new security group and disable the deletion protection as well.<\/p>\n\n\n\n

Finally, we will enter a username and password that will be used to log in to the DB instance. We will then add a new AWS region to create a Secondary cluster of the Primary database. On successful creation of the Primary and Secondary clusters, we will log in to the Primary database instance using the writer instance\u2019s endpoint and a MySQL command on the MySQL Command Line Client terminal. On the prompt, you will be required to enter the password for the database instance that you configured while creating the instance. Then we will create a new schema on the primary cluster. Activating the newly created schema, we will then create a new table inserting values in the table. You can run the select query to check if the values have been stored successfully in the created table. We will then copy the secondary instance\u2019s reader endpoint and use the same in a new MySQL Command Line Client terminal to log in to the Secondary database.<\/p>\n\n\n\n

On the prompt, you will be required to enter the password for the database instance that you configured while creating the instance. Activating the primary cluster\u2019s schema, we will check if the schema that was created in the primary cluster is successfully cloned to the secondary cluster or not. On success, we will execute a select query on the newly created table in that schema to check if the data inside the table is replicated successfully or not. Post that, we will perform the Failover Global Database action to make the Secondary cluster the Primary cluster and vice versa. On successful transition, we will then finally check the roles of the final instances.<\/p>\n\n\n\n

To implement the same, we will do the following:<\/strong><\/p>\n\n\n\n