Amazon RDS now supports renaming Multi-AZ deployments with two readable standbys
Amazon Relational Database Service (Amazon RDS) now supports renaming Amazon RDS Multi-AZ deployments with two readable standbys. The ability to rename the RDS Multi-AZ deployments with two readable standbys helps you to replace a deployment without having to change any application code that references the deployment by name such as the connection endpoint. Renaming is used when you restore data from a DB snapshot, or when you do a point-in-time recovery (PITR).
Amazon Relational Database Service (Amazon RDS) now supports renaming Amazon RDS Multi-AZ deployments with two readable standbys. The ability to rename the RDS Multi-AZ deployments with two readable standbys helps you to replace a deployment without having to change any application code that references the deployment by name such as the connection endpoint. Renaming is used when you restore data from a DB snapshot, or when you do a point-in-time recovery (PITR).
Amazon RDS Multi-AZ deployments provide enhanced availability and durability, making them a natural fit for production database workloads. Deployment of Amazon RDS Multi-AZ with two readable standbys supports up to 2x faster transaction commit latencies than a Multi-AZ deployment with one standby instance. In this configuration, automated failovers typically take under 35 seconds. In addition, the two readable standbys can also serve read traffic without needing to attach additional read replicas.
For a full list of the Amazon RDS Multi-AZ with two readable standbys regional availability and supported engine versions, refer the Amazon RDS User Guide.
Learn more about Amazon RDS Multi-AZ deployments in the Amazon RDS User Guide and in the AWS News Blog. Create or update a fully managed Amazon RDS Multi-AZ database with two readable standby instances in the Amazon RDS Management Console.