Changing a DB Instance Type from Single-Node to Primary/Standby

Scenarios

• RDS enables you to change single-node DB instances to primary/standby DB instances to improve instance reliability.
• Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly.
• Anti-affinity deployment is supported for primary/standby DB instances to prevent the entire instance unavailability due to the failure of a single host.

Precautions

Changing a single-node instance to primary/standby does not change its networking information, including the VPC, subnet, security group, private IP address, private domain name, and database port.

Procedure

1. Log in to the management console.
2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
3. On the Instances page, locate a single-node DB instance and choose More > Change Type to Primary/Standby in the Operation column.
4. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.

   It is recommended that the standby AZ be different from the primary AZ to provide failover and high availability.

5. Check the instance status on the Instances page.
   • The DB instance is in the Changing type to primary/standby status. You can view the progress on the Task Center page. For details, see Task Center.
   • In the upper right corner of the DB instance list, click to refresh the list. After the DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.