This topic describes the items that you can configure for an ApsaraDB RDS for MySQL instance.
|RDS edition||Only the following downgrade and upgrade scenarios are supported:
Note If none of the preceding downgrade and upgrade scenarios meets your business requirements, you can create an RDS instance that runs the required RDS edition. Then, you can migrate the data of your original 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. If your RDS instance runs the RDS High-availability Edition with local SSDs, you can also decrease the storage capacity of your RDS instance.
You can migrate your RDS instance across zones in the same region. After the migration process is complete, the attributes, configuration, and endpoints of your RDS instance remain unchanged.
If your RDS instance runs MySQL 5.7 on RDS High-availability Edition, you must change the zone of your RDS instance when you upgrade the RDS edition to the RDS Enterprise Edition.
Note During the cross-zone migration process, ApsaraDB RDS migrates the data of your RDS instance from the original zone to the new zone that you specify. 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 ApsaraDB RDS to automatically switch workloads over between your RDS instance and its secondary RDS instance. You can also manually switch workloads over between your RDS instance and its secondary RDS instance. After the switchover is complete, your RDS instance is demoted to run as the new secondary RDS instance.||Switch workloads over between primary and secondary ApsaraDB RDS for MySQL instances|
|Network type||All RDS instances can be deployed in virtual private clouds (VPCs). Only the RDS instances that meet specific requirements can be deployed in the classic network. If your RDS instance supports both the VPC network type and the classic network type, you can switch between the network types.||Change the network type of an ApsaraDB RDS for MySQL instance|
|VPC and vSwitch||If your RDS instance meets specific requirements, you can change the VPC or vSwitch of your RDS instance.||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 mode based on which your RDS instance replicates data to its secondary RDS instance. This way, you can improve the availability of your database service.||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.||For more information, see 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 major engine version of an ApsaraDB RDS for MySQL instance|
|Billing method||You can change the billing method of your RDS instance between pay-as-you-go and subscription.||Switch an ApsaraDB RDS for MySQL instance from pay-as-you-go to subscription|
|Region||After your RDS instance is created, you cannot change the region of the instance. If you want to deploy your database service in a different region, you can create an RDS instance in the region. Then, you can migrate the data of your original RDS instance to the new RDS instance by using DTS. After the data migration process is complete, you must update the endpoint configuration on your application and verify that your workloads run as expected 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|