This topic describes the items that you can configure for an ApsaraDB RDS for MySQL instance.
Computing and storage
Instance type
Description | Change method |
You can change the instance type of your RDS instance regardless of the instance configuration. Note If the instance type of your RDS instance is phased out and cannot be directly changed, you can perform the following steps:
|
Storage type
Description | Change method |
The following changes are supported:
| Upgrade the storage type from standard SSD to ESSD Upgrade the RDS edition from RDS Basic Edition to RDS High-availability Edition |
Storage capacity
Operation type | Description | Change method |
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. Note If your RDS instance uses cloud disks and does not run RDS Basic Edition, you can expand the storage capacity of your RDS instance with no downtime. In most cases, no transient connections occur when you expand the storage capacity. | |
Storage capacity reduction |
| Local disks: Change instance specifications Cloud disks: Reduce the storage capacity of an ApsaraDB RDS for MySQL instance that uses cloud disks |
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 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.
Region and zone
Configuration item | Description | Change method |
Region | After your RDS instance is created, you cannot change the region of your RDS instance. If you want to deploy your database service in a different region, you can create an RDS instance in the required region. Then, 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 in 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. | |
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. When you upgrade the RDS edition of your RDS instance that runs MySQL 5.7 from RDS High-availability Edition to RDS Enterprise Edition, you must change the zone of the RDS instance. Note
| Migrate an ApsaraDB RDS for MySQL instance across zones in the same region |
RDS edition and product type
Configuration item | Description | Change method |
RDS edition | Only the following downgrade and upgrade scenarios are supported:
Note
| Change instance specifications Upgrade the RDS edition from RDS Basic Edition to RDS High-availability Edition Upgrade an ApsaraDB RDS for MySQL instance from RDS High-availability Edition to RDS Cluster Edition |
Product type | You can change the product type of your RDS instance between economy and standard. For more information, see Product types. Note
|
Networking
Configuration item | Description | Change method |
Network types | 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 |
Primary/secondary switchover
Configuration item | Description | Change method |
Primary/secondary switchover | You can configure the system 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 |
Data replication mode | You can change the mode based on which the primary RDS instance replicates data to its secondary RDS instance to improve the availability of your database service. |
Parameter configuration
Description | Change method |
You can modify some parameters of your RDS instance based on your business requirements. | 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
Description | Change method |
You can perform the following upgrades in the ApsaraDB RDS console:
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 |
Maintenance window
Description | Change method |
You can change the maintenance window of your RDS instance. | Set the maintenance window of an ApsaraDB RDS for MySQL instance |
Billing method
Description | Change method |
You can change the billing method of your RDS instance between pay-as-you-go and subscription. | Switch from pay-as-you-go to subscription Change the billing method of an ApsaraDB RDS instance from subscription to pay-as-you-go |