Configuration items for an ApsaraDB RDS for MySQL instance - ApsaraDB RDS

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


Configuration item	Description	References
Region	After your RDS instance is created, you cannot change the region in which your RDS instance resides. If you want to deploy your database service in a different region, you can create an RDS instance in the required region. 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
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 RDS High-availability Edition. If your RDS instance runs MySQL 5.7 or MySQL 8.0 on RDS Basic Edition, you can upgrade the RDS edition of the instance to RDS High-availability Edition. If your RDS instance runs MySQL 5.7 or MySQL 8.0 on RDS High-availability Edition, you can upgrade the RDS edition of the instance to RDS Cluster Edition. Note If your RDS instance does not meet the preceding conditions, you cannot upgrade or downgrade the RDS edition of your RDS instance. If none of the preceding downgrade and upgrade scenarios meets your business requirements, you can perform the following steps: Create an RDS instance. When you configure the parameters for the RDS instance, select the RDS edition that you want to use. For more information, see Create an ApsaraDB RDS for MySQL instance. 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. Release the 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 Upgrade an ApsaraDB RDS for MySQL instance from Basic Edition to High-availability Edition Upgrade an ApsaraDB RDS for MySQL instance from RDS High-availability Edition to RDS Cluster Edition
Architecture	You can change the architecture of your RDS instance between x86 and ARM. For more information about the differences between x86 and ARM, see Architectures. Note If you cannot select the required architecture when you change the configuration of the RDS instance, no resources are available in the zone in which the RDS instance resides. You can go to the ApsaraDB RDS buy page to view the zones that are supported for the required architecture, migrate the RDS instance to a zone that can provide the required resources, and then change the configuration. For more information, see Migrate an ApsaraDB RDS for PostgreSQL instance across zones in the same region. If you want to change the architecture of an RDS instance, make sure that the required minor engine version of the RDS instance is later than or equal to the current minor engine version. If the current minor engine version of the RDS instance is later than the required minor engine version, you cannot change the architecture.	Specification changes
Instance type	You can change the instance types of all RDS instances. Note If the specifications of your RDS instance are outdated and cannot be directly changed, you can perform the following steps: 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. 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. Release the 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	If your RDS instance runs MySQL 8.0 or MySQL 5.7 on RDS Basic Edition or RDS High-availability Edition and uses the standard SSD storage type, you can change the storage type to enhanced SSD (ESSD). When you upgrade the RDS edition of your RDS instance that runs RDS Basic Edition to the RDS High-availability Edition, you can change the storage type to local SSD. This operation is supported only when your RDS instance runs MySQL 5.7 with standard SSDs.	Upgrade the storage type of an ApsaraDB RDS for MySQL instance from standard SSDs to ESSDs Upgrade an ApsaraDB RDS for MySQL instance from Basic Edition to High-availability Edition
Storage capacity	You can expand or reduce the storage capacity of an RDS instance. Storage capacity expansion: You can expand the storage capacity at a step size of 5 GB. The new storage capacity cannot be greater than the maximum storage capacity that is supported by the instance type of the RDS instance. For more information, see Primary ApsaraDB RDS instance types. Storage capacity reduction: If your RDS instance runs RDS High-availability Edition and uses local disks, you can reduce the storage capacity. If your RDS instance runs RDS Basic Edition or RDS High-availability Edition and uses cloud disks, you can reduce the storage capacity without the need to change the RDS edition or architecture of the RDS instance. The minimum storage capacity after the storage capacity reduction must be greater than or equal to the minimum storage capacity that is supported by the instance type of the RDS instance. You can use the following formula to calculate the minimum storage capacity to which you can reduce your RDS instance: `min{Used storage × 1.3, Used storage + 400 GB}`. You can reduce the storage capacity at a step size of 5 GB. Note The storage capacity reduction feature for RDS instances that use cloud disks is available in phases. The available regions are displayed on the Change Specifications page. You can reduce the storage capacity of an RDS instance only when the instance runs MySQL 5.7 or MySQL 8.0 and a minor engine version of 20210430 or later. For more information, see Reduce the storage capacity of an ApsaraDB RDS for MySQL instance that uses ESSDs. Examples of storage capacity reduction Your RDS instance uses a PL1 ESSD that provides 2,000 GB of storage capacity. The minimum storage capacity that is supported by the instance type of the RDS instance is 20 GB. The minimum storage capacity to which you can reduce your RDS instance varies based on the storage usage. If 10 GB of storage is used, the value obtained by using the preceding formula is 13 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 20 GB. If 500 GB of storage is used, the value obtained by using the preceding formula is 650 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 650 GB. If 1,500 GB of storage is used, the value obtained by using the preceding formula is 1,900 GB. In this case, the minimum storage capacity to which you can reduce your RDS instance is 1,900 GB. Note The storage capacity of a read-only RDS instance must be greater than or equal to the storage capacity of its primary RDS instance. If your RDS instance uses cloud disks and does not run 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. If the storage capacity range that is supported by the instance type of an RDS instance does not meet your business requirements, we recommend that you select another instance type.	Change the specifications of an ApsaraDB RDS for MySQL instance Configure automatic storage expansion for an ApsaraDB RDS for MySQL instance Reduce the storage capacity of an ApsaraDB RDS for MySQL instance that uses ESSDs
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, configurations, 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 RDS Enterprise Edition. Note Cross-zone migration is not supported for RDS Cluster Edition. During the cross-zone migration, the system migrates the data of your RDS instance from the original zone to the new zone that you specify. The period 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, the original primary 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.	Change the VPC and vSwitch for an ApsaraDB RDS for MySQL instance
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 the primary RDS instance replicates data to its secondary RDS instance. This way, you can improve the availability of your database service.	Change of the data replication mode
Instance parameter configuration	You can modify some parameters of your RDS instance based on your business requirements.	For more information, see Modify the parameters of an ApsaraDB RDS for MySQL instance or Use a parameter template to configure the parameters of ApsaraDB RDS for MySQL instances.
Database engine version	You can perform the following upgrades in the ApsaraDB RDS console: Upgrade from MySQL 5.7 to MySQL 8.0 Upgrade from MySQL 5.6 to MySQL 5.7 Upgrade from MySQL 5.5 to MySQL 5.6 Note You can upgrade the major engine version of an RDS instance only to the next major engine version. For example, you cannot directly upgrade the major engine version of your RDS instance from MySQL 5.5 to MySQL 8.0.	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.	Change the billing method of an ApsaraDB RDS for MySQL instance from pay-as-you-go to subscription Change the billing method of an ApsaraDB RDS instance from subscription to pay-as-you-go