This topic describes the items that you can configure for an ApsaraDB RDS for MySQL instance.

Configuration item Description References
RDS edition Only the following downgrade and upgrade scenarios are supported:
  • If your RDS instance runs MySQL 5.6 on RDS Enterprise Edition, you can downgrade the RDS edition of the instance to the High-availability Edition.
  • If your RDS instance runs MySQL 5.7 or MySQL 8.0 on RDS Basic Edition, you can downgrade the RDS edition of the instance to the High-availability Edition.
Note

Change the specifications of an ApsaraDB RDS for MySQL instance

Upgrade an ApsaraDB RDS for MySQL instance from Basic Edition to High-availability Edition

Instance type You can change the instance type of your RDS instance regardless of the instance configuration.
Note If the specifications of your RDS instance are outdated and cannot be directly changed, you can perform the following steps:
  1. Create an RDS instance. When you configure the parameters for the RDS instance, select the instance type that you want to use. For more information, see Create an ApsaraDB RDS for MySQL instance.
  2. Migrate the data of your original RDS instance to the new RDS instance. For more information, see Migrate data between ApsaraDB RDS for MySQL instances.
  3. Release your original RDS instance. For more information, see Release or unsubscribe from an ApsaraDB RDS for MySQL instance.
Change the specifications of an ApsaraDB RDS for MySQL instance

Enable the automatic scale-up feature for an ApsaraDB RDS for MySQL instance

Storage type When you upgrade the RDS edition of your RDS instance to the High-availability Edition, you can change the storage type to local SSDs at the same time. This operation is supported only when your RDS instance runs RDS Basic Edition on MySQL 5.7 with standard SSDs. Upgrade an ApsaraDB RDS for MySQL instance from Basic Edition to High-availability Edition
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.
Note
  • You can decrease the storage capacity of your RDS instance only when your RDS instance runs the RDS High-availability Edition with local SSDs.
  • If your RDS instance is equipped with standard SSDs or enhanced SSDs (ESSDs) and does not run the RDS Basic Edition, you can increase the storage capacity of your RDS instance with no downtime. In most cases, no transient connections occur when you increase the storage capacity.
  • The new storage capacity of your RDS instance cannot exceed the maximum storage capacity that is supported by the selected instance type. If the maximum storage capacity that is supported by the instance type cannot meet your business requirements, you can upgrade the instance type of your RDS instance. For more information, see Primary ApsaraDB RDS instance types.
Change the specifications of an ApsaraDB RDS for MySQL instance

Configure automatic storage expansion for an ApsaraDB RDS for MySQL instance

Zone

You can migrate your RDS instance across zones within the same region. After your RDS instance is migrated to a different zone, 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 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. The amount of time that is required to migrate data increases with the amount of data that needs to be migrated.
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 the network type of your RDS instance between VPC and classic network. 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 based on 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 directly upgrade the database engine version of your RDS instance only from MySQL 5.5 to MySQL 5.6. A new version is available
Billing method You can switch 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

Switch an ApsaraDB RDS for MySQL instance from subscription to pay-as-you-go

Region After your RDS instance is created, you cannot change the region where your RDS instance resides. If you want to deploy your database service in a different region, you can create an RDS instance in the region that you want. Then, you can migrate the data of your original RDS instance to the new RDS instance by using Data Transmission Service (DTS). After the data is migrated, 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