Add and manage RDS read replicas
Create a read replica of your RDS database
Last updated
Create a read replica of your RDS database
Last updated
© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates
Creating AWS RDS read replicas of your database helps you elastically scale your capacity to handle read-heavy workloads and ensure that your application can efficiently serve growing requests. Read replicas distribute read traffic across multiple instances, boosting performance by increasing aggregate read throughput and reducing the load on the primary database. Additionally, should the need arise, you can promote a read replica to a standalone database instance, enabling seamless failover and enhancing your overall database availability and resilience.
In the DuploCloud Portal, navigate to Cloud Services -> Database.
Click the RDS tab.
Click on the name of the database you want to replicate in the NAME column.
From the Actions menu, select RDS Settings, and then Add Replica. The Add read replica to: DATABASE pane displays.
In the Read Replica Name field, provide a name for the replica (the Tenant name is prefixed automatically).
From the Instance Size list box, choose a size that meets or exceeds the specifications of the database you are replicating.
Click Create. Your replica displays on the RDS tab with a status of Submitted. When the replica is ready for use, the status changes to Available.
Transforming a read replica into a standalone primary instance allows it to accept write operations and maintain data integrity without relying on the original primary. This enhances database availability and efficient scaling. DuploCloud supports promoting read replicas for PostgreSQL, MySQL, and MariaDB databases.
In the DuploCloud Portal, navigate to Cloud Services -> Database.
Select the RDS tab.
Click on the name of the database you want to promote from the NAME column.
In the Actions menu, select RDS Settings, and then Promote Replica.
Click Confirm in the confirmation dialog box. The promoted replica stops replicating from the primary instance and becomes a standalone database that can accept write operations.