All Products
Search
Document Center

ApsaraDB RDS:Configuration items

Last Updated:Jul 24, 2024

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:

  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 the original RDS instance. For more information, see Release or unsubscribe from an ApsaraDB RDS for MySQL instance.

Change instance specifications

Configure the automatic performance scaling feature

Storage type

Description

Change method

The following changes are supported:

  • 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 Enterprise SSD (ESSD).

  • If your RDS instance runs MySQL 8.0 or MySQL 5.7 on RDS High-availability Edition and uses the local disk storage type, you can change the storage type to ESSD.

  • When you upgrade the RDS edition of your RDS instance that runs RDS Basic Edition to RDS High-availability Edition, you can change the storage type to local disk. This operation is supported only when your RDS instance runs MySQL 5.7 with standard SSDs.

  • If you RDS instance uses an ESSD that provides at least 40 GB of storage capacity, you can change the storage type to general ESSD.

  • If your RDS instance runs RDS Basic Edition, you can change the storage type between PL0 ESSD and PL1 ESSD. If your RDS instance runs RDS High-availability Edition, you can change the storage type between PL1 ESSD, PL2 ESSD, and PL3 ESSD.

  • If your RDS instance runs RDS Cluster Edition, you can change the storage type between PL1 ESSD, PL2 ESSD, and PL3 ESSD.

Upgrade the storage type from standard SSD to ESSD

Change the storage type from local SSD to ESSD

Upgrade the RDS edition from RDS Basic Edition to RDS High-availability Edition

Change the storage type from ESSD to general ESSD

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.

Change instance specifications

Configure automatic storage expansion

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, RDS High-availability Edition, or RDS Cluster 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 run RDS Cluster Edition with cloud disks is available only in the Singapore region. This feature is available in phases. You can view the available regions 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.

    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.

Local disks: Change instance specifications

Cloud disks: How do I reduce the storage capacity of an ApsaraDB RDS for MySQL instance that uses cloud disks?

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 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.

Migrate data between ApsaraDB RDS for MySQL instances

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
  • Cross-zone migration is not supported for RDS instances that run 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

RDS edition and product type

Configuration item

Description

Change method

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 RDS 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 RDS 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 RDS instance to RDS Cluster Edition.

Note

Change instance specifications

Upgrade the RDS edition from RDS Basic Edition to RDS High-availability Edition

Upgrade an RDS instance from RDS High-availability Edition to RDS Cluster Edition

Product type

You can change the product type of your RDS instance between YiTian and standard. For more information, see Product types.

Note
  • If you cannot select the required product type 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 support the required product type, migrate the RDS instance to a zone that can provide the required resources, and then change the product type. For more information, see Migrate an ApsaraDB RDS for PostgreSQL instance across zones in the same region.

  • If you want to change the product type of your RDS instance, make sure that the minor engine version of the RDS instance after the change is later than or the same as the current minor engine version. If the minor engine version after the change is earlier than the current minor engine version, the product type change fails.

Change instance specifications

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

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

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.

Query and change the data replication mode

Parameter configuration

Description

Change method

You can modify some parameters of your RDS instance based on your business requirements.

Modify instance parameters or Use a parameter template

Database engine version

Description

Change method

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

Maintenance window

Description

Change method

You can change the maintenance window of your RDS instance.

Configure a maintenance window

Billing method

Description

Change 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 from subscription to pay-as-you-go