All Products
Search

This Product

    ApsaraDB RDS:Configuration items

    Document Center

    ApsaraDB RDS:Configuration items

    Last Updated:Mar 28, 2026

    This page lists the configuration items you can change on an ApsaraDB RDS for MySQL instance, along with the constraints and how to make each change.

    Computing and storage

    Instance type

    DescriptionChange method
    All instances support instance type changes. Some legacy instance types cannot be changed directly. If a direct change is not available, create a new instance with the target type, migrate data from the original instance, and then release the original instance.Change configurations or configure automatic performance scaling

    Storage type

    DescriptionChange method
    The following storage type changes are supported:
    • MySQL 8.0 or 5.7 on High-availability Edition or Basic Edition with standard SSDs: change to ESSD.
    • MySQL 8.0 or 5.7 on High-availability Edition with premium local disks: change to ESSD.
    • MySQL 5.7 Basic Edition (standard SSDs) upgraded to High-availability Edition: can also change to premium local disks during the upgrade.
    • ESSD with at least 40 GB of storage: change to premium performance disk.
    • Basic Edition: change from PL0 ESSD to PL1 ESSD only (not the reverse).
    • High-availability Edition and Cluster Edition nodes: switch between PL1, PL2, and PL3 ESSDs.
    		Upgrade from standard SSD to ESSD / Change from premium local disk to cloud disk / Upgrade from Basic Edition to High-availability Edition / Change from ESSD to premium performance disk

    Storage capacity

    OperationDescriptionChange method
    Scale-outIncrease storage capacity by at least 5 GB. The new capacity cannot exceed the maximum for the current instance type. See Primary instance types for supported ranges.
    Note

    Instances using cloud disks (except Basic Edition) support online storage expansion. In most cases, this does not cause transient connections.

    Note

    For instances that use cloud disks and are not Basic Edition, you can increase the storage capacity online. In most cases, this operation does not cause transient connections.

    		Change configurations or configure automatic storage expansion
    Scale-inPremium local disks: High-availability Edition instances with local disks can reduce storage capacity. Cloud disks: Basic Edition, High-availability Edition, and Cluster Edition instances can reduce storage capacity within the same edition and architecture. The minimum capacity you can reduce to is calculated as min{Used storage × 1.3, Used storage + 400 GB}, and cannot be smaller than the minimum supported by the current instance type. Adjustments must be in 5 GB increments. Constraints:
    • For Cluster Edition (cloud disks), scale-in is currently supported only in the Singapore region and is being rolled out to other regions.
    • Supported only for MySQL 5.7 or 8.0 with minor engine version 20210430 or later.
    Examples (PL1 ESSD with 2,000 GB total, minimum instance type storage 20 GB):
    • 10 GB used: min{13, 410} = 13 GB, which is less than the 20 GB minimum — reduce to 20 GB.
    • 500 GB used: min{650, 900} = 650 GB — reduce to 650 GB.
    • 1,500 GB used: min{1950, 1900} = 1,900 GB — reduce to 1,900 GB.
    		Premium local disks: Change configurations Cloud disks: Reduce the capacity of an ESSD
    The storage capacity of a read-only instance must be greater than or equal to that of its primary instance. If the storage capacity range of the current instance type does not meet your requirements, change the instance type first.

    Region and zone

    Configuration itemDescriptionChange method
    RegionThe region of an instance cannot be changed after it is created. To move to a different region, create an instance in the target region, migrate data using Data Transmission Service (DTS), update the endpoint in your application, verify that your business runs as expected, and then release the original instance.Migrate data
    ZoneInstances can be migrated to another zone in the same region. After migration, all properties, configurations, and endpoints remain unchanged. When upgrading a MySQL 5.7 instance from High-availability Edition to RDS Enterprise Edition (formerly Finance Edition), a zone change is required. Constraints:
    • Cluster Edition instances cannot be migrated across zones.
    • Zone migration requires data migration. The time taken depends on the amount of data.
    		Migrate an instance across zones

    RDS edition and product type

    Configuration itemDescriptionChange method
    Product seriesThe following RDS edition upgrades are supported:
    • MySQL 5.6 RDS Enterprise Edition → High-availability Edition
    • MySQL 8.0 and 5.7 Basic Edition → High-availability Edition
    • MySQL 8.0 and 5.7 High-availability Edition → Cluster Edition
    Other edition changes are not supported directly. To change to an unsupported edition, create a new instance with the target edition, migrate data, and then release the original instance.    		Change from RDS Enterprise Edition to High-availability Edition (MySQL 5.6) / Upgrade from Basic Edition to High-availability Edition / Upgrade from High-availability Edition to Cluster Edition
    Product type
    • High-availability Edition and Cluster Edition: switch between Standard Edition and Yitian Edition.
    • Basic Edition: change from Yitian Edition to Standard Edition only.
    Constraints:
    • If the target product type is unavailable, resources for that type may not be available in the current zone. Check available zones on the instance purchase page, use the Migrate Zone feature to move the instance to a supported zone, and then change the configuration.
    • The minor engine version after the change must be the same as or later than the current version. A change is not allowed if the new minor engine version would be earlier.
    		Change configurations

    Networking

    Configuration itemDescriptionChange method
    VPC and vSwitchFor some instances, the VPC and vSwitch can be switched.Switch the VPC and vSwitch

    Primary and secondary instances

    Configuration itemDescriptionChange method
    Primary/secondary relationshipAutomatic and manual primary/secondary failovers are supported. After a failover, the original primary instance becomes the secondary instance.Manage primary/secondary failovers
    Data replication modeChange the data replication mode between primary and secondary instances to improve database availability.Query and change the data replication mode

    Instance parameters

    DescriptionChange method
    Modify instance parameters to meet your business needs.Set instance parameters or use a parameter template

    Database engine version

    DescriptionChange method
    The following major version upgrades are supported in the console:
    • MySQL 5.7 → MySQL 8.0
    • MySQL 5.6 → MySQL 5.7
    • MySQL 5.5 → MySQL 5.6
    Upgrades must be sequential. Skipping versions (for example, upgrading directly from MySQL 5.5 to MySQL 8.0) is not supported.    		Upgrade the database engine version

    Maintenance window

    DescriptionChange method
    Change the maintenance window of an instance.Set a maintenance window

    Billing method

    DescriptionChange method
    Switch an instance's billing method between pay-as-you-go and subscription.Change from pay-as-you-go to subscription or change from subscription to pay-as-you-go