This topic provides an overview of the items that you can reconfigure for an ApsaraDB RDS for MySQL instance.
|RDS edition||Only the following changes are supported:
Note If you want to perform a change that involves other RDS editions, you can create an RDS instance that runs the required RDS edition. Then, you can migrate the data of your RDS instance to the new RDS instance by using Data Transmission Service (DTS). For more information, see Create an ApsaraDB RDS for MySQL instance and Migrate data between ApsaraDB RDS for MySQL instances.
|Instance type||You can change the instance type of your RDS instance regardless of the instance configuration.||Change the specifications of an ApsaraDB RDS for MySQL instance|
|Storage capacity||You can increase the storage capacity of your RDS instance regardless of the instance configuration.|
You can migrate your RDS instance across zones in the same region. After the migration is completed, the attributes, configuration, and endpoints of your RDS instance remain unchanged.
When you upgrade the RDS edition from High-availability to Enterprise, you must change the zone. This applies if your RDS instance runs MySQL 5.7.
Note When you migrate your RDS instance across zones, a data migration is triggered. A larger data volume indicates a longer period of time that is required to complete the data migration.
|Migrate an ApsaraDB RDS for MySQL instance across zones in the same region|
|Primary/secondary switchover||You can configure automatic switchovers or perform manual switchovers between your RDS instance and its secondary RDS instance. After the switchover is completed, the role of your RDS instance changes to secondary.||Perform a manual or automatic switchover of services between a primary ApsaraDB RDS for MySQL instance and its secondary instance|
|Network type||All RDS instances can be deployed in virtual private clouds (VPCs). Some RDS instances can also be deployed in the classic network. If your RDS instance supports both the VPC and classic network types, you can switch your RDS instance between these network types.||Change the network type of an ApsaraDB RDS for MySQL instance|
|VPC and vSwitch||Some RDS instances support changes to their VPCs and vSwitches.||Switch an ApsaraDB RDS for MySQL instance to a new VPC and a new vSwitch|
|Maintenance window||You can change the maintenance window of your RDS instance.||Set the maintenance window of an ApsaraDB RDS for MySQL instance|
|Data replication mode||You can change the data replication mode of your RDS instance and its secondary RDS instance. This improves service availability.||Change the data replication mode of an ApsaraDB RDS for MySQL instance|
|Instance parameter configuration||You can reconfigure some parameters of your RDS instance to better meet your business requirements.||Reconfigure the parameters of an ApsaraDB RDS for MySQL instance or Use a parameter template to manage parameters|
|Database engine version||You can upgrade the database engine version of your RDS instance only from MySQL 5.5 to MySQL 5.6.||Upgrade the database engine version of an ApsaraDB RDS for MySQL instance|
|Billing method||You can switch your RDS instance between the pay-as-you-go and subscription billing methods.||Switch an ApsaraDB RDS for MySQL instance from pay-as-you-go to subscription|
|Region||After your RDS instance is created, you cannot change its region. If you want to deploy your database service in a specific region, you can create an RDS instance in the region. Then, you can migrate the data of your RDS instance to the new RDS instance by using DTS. After the data migration is completed, you must update the endpoint configuration on your application and verify that your workloads run as normal on the new RDS instance. Then, you can release your original RDS instance. For more information, see Release or unsubscribe from an ApsaraDB RDS for MySQL instance.||Migrate data between ApsaraDB RDS for MySQL instances|