Which of the following are benefits of Amazon RDS Read replicas?
Amazon RDS Read Replicas provide enhanced performance and durability for RDS database (DB) instances. They make it easy to elastically scale out beyond the capacity constraints of a single DB instance for read-heavy database workloads.
Where are RDS backups stored?
S3
Amazon RDS DB snapshots and automated backups are stored in S3. You can use the AWS Management Console, the ModifyDBInstance API, or the modify-db-instance command to manage the period of time your automated backups are retained by modifying the RetentionPeriod parameter.
How are read replicas used in Amazon RDS?
Updates made to the source database are then asynchronously copied to your Read Replicas. In addition to providing scalability for read-heavy workloads, Read Replicas can be promoted to become a standalone database instance when needed. Amazon RDS Multi-AZ deployments provide enhanced availability for database instances within a single AWS Region.
When to promote a Read Replica to a standalone instance?
You can promote a read replica to a standalone instance as a disaster recovery solution if the primary DB instance fails. By default, a read replica is created with the same storage type as the source DB instance.
When to use Amazon RDS for disaster recovery?
For a production environment, it is important to take precautions so that you can recover if there’s an unexpected event. While Amazon RDS provides a highly available Multi-AZ configuration, it can’t protect from every possibility, such as a natural disaster, a malicious actor, or logical corruption of a database.
Can a Read Replica be created from a DB instance?
For example, from ReadReplica1, you can create a new read replica, such as ReadReplica2. For Oracle, PostgreSQL, and SQL Server, you can’t create a read replica from an existing read replica. If you no longer need read replicas, you can explicitly delete them using the same mechanisms for deleting a DB instance.