This topic describes the release notes for ApsaraDB RDS for MySQL and provides links to the relevant references.
For more information about the release notes for AliSQL, see Release notes for AliSQL.
2024
October
Category | Feature | Description | Release date | References |
New feature | Instance types of standard primary ApsaraDB RDS for MySQL instances | The mysql.x2.8xlarge.xc instance type that provides 64 CPU cores and 128 GB of memory and the mysql.x4.8xlarge.xc instance type that provides 64 CPU cores and 256 GB of memory are supported for standard (originally known as x86 architecture) primary ApsaraDB RDS for MySQL instances that run RDS Cluster Edition. | 10-18 | Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture) |
September
Category | Feature | Description | Release date | References |
New feature | Restoration of individual databases and tables | ApsaraDB RDS for MySQL Cluster Edition instances support the restoration feature for individual databases and tables. This feature can be used in scenarios in which misoperations are performed and data needs to be quickly restored or scenarios in which historical data needs to be analyzed. | 09-14 | |
New feature | Column encryption | Column encryption rules and role permissions can be configured for an ApsaraDB RDS for MySQL instance in the ApsaraDB RDS console. | 09-13 | Configure column encryption rules in the ApsaraDB RDS console |
Feature optimization | Major engine version upgrade | The major engine version of an RDS instance can be upgraded from MySQL 5.7 to MySQL 8.0. This applies if the RDS instance runs RDS Cluster Edition or runs RDS High-availability Edition with read-only RDS instances attached. | 09-01 |
August
Category | Feature | Description | Release date | References |
Feature optimization | Node addition | When you add a node to an RDS cluster, the instance type of the node can be different from the instance type of the primary node. | 08-30 | |
New feature | Database proxy | If your database proxy version is 2.9.1 or later, connection pooling and a latency threshold can be configured for the database proxy endpoint that uses the read-only attribute. | 08-29 | |
New feature | Database proxy | The database proxy feature can be enabled on the ApsaraDB RDS buy page. | 08-13 | |
New feature | Database proxy | Starting August 1, 2024, persistent connections are supported during the failover of an ApsaraDB RDS for MySQL instance for which the version of the database proxy is 2.9.1. This reduces the risk of connection interruptions and improves the connection reliability. | 08-01 |
July
Category | Feature | Description | Release date | References |
Feature optimization | Automatic performance scaling | The automatic performance scaling feature is supported for RDS instances that run RDS High-availability Edition and use general-purpose instance types and local disks. As your business grows, data volume increases, and new services or new features are released, the database traffic increases and computing resources become insufficient. Increasing the database computing resources, such as CPU cores and memory resources, is an effective method to resolve the problems. The computing specifications can be automatically increased for RDS instances that run RDS High-availability Edition and use general-purpose instance types and local or cloud disks to handle traffic spikes. When traffic decreases, DAS automatically scales down the instance specifications to prevent inefficient use of resources. | 07-05 | |
New feature | Custom certificate | The SSL encryption feature can be used to encrypt data that is transmitted between ApsaraDB RDS for MySQL instances and clients. This prevents data from being monitored, intercepted, or tampered with by third parties. When you configure SSL encryption for an ApsaraDB RDS for MySQL instance, you can use custom certificates as well as certificates that are managed by Alibaba Cloud. | 07-02 |
June
Category | Feature | Description | Release date | References |
New feature | Zero-ETL | ApsaraDB RDS provides the zero-ETL feature to synchronize data from an ApsaraDB RDS for MySQL instance to a data warehouse. You do not need to create or maintain data synchronization tasks, and you are not charged for data synchronization tasks. This reduces data transmission costs and O&M costs. The data warehouse can be an AnalyticDB for MySQL cluster or an ApsaraDB for ClickHouse cluster. | 06-30 | |
New feature | YiTian product type |
| 06-30 | |
New feature | Persistent connection | Starting June 27, 2024, persistent connections are supported by the database proxy feature for ApsaraDB RDS for MySQL instances that run RDS Cluster Edition. | 06-27 | |
New feature | Read-only instance management | Starting June 20, 2024, ApsaraDB RDS for MySQL provides standard read-only RDS instances that run RDS Basic Edition. To offload read requests from the primary RDS instance, you can create one or more read-only RDS instances. Read-only RDS instances help increase the read capability of your database system and the throughput of your application. | 06-20 | |
New feature | MySQL version upgrade | The precheck is supported before you upgrade the MySQL version of your RDS instance. | 06-20 | |
New feature | General ESSDs | The general Enterprise SSD (ESSD) is a new storage type supported by ApsaraDB RDS. General ESSDs are compatible with all features of ESSDs and support the I/O burst, I/O acceleration, and data archiving features. | 06-20 | |
New feature | Serverless | The billing method of an RDS instance that uses general ESSDs can be changed between pay-as-you-go and serverless. | 06-06 | |
New feature | Serverless | The cloud disk encryption feature is supported for serverless RDS instances. | 06-06 | |
Feature optimization | MySQL version upgrade | The limit on SSL validation is deleted when you upgrade the MySQL version of your RDS instance. | 06-03 |
May
Category | Feature | Description | Release date | References |
New feature | The YiTian product type is supported for ApsaraDB RDS instances that run MySQL 5.7 | The YiTian product type is developed based on the ARM architecture that uses Alibaba Cloud-developed YiTian chips to provide ultra-high cost-effectiveness. The YiTian product type allows you to create RDS instances in a quick manner and helps reduce IT investment and costs. | 05-29 | |
New feature | Instance type for YiTian primary ApsaraDB RDS for MySQL instances | YiTian primary ApsaraDB RDS for MySQL instances are newly available for purchase in the following zone: Hong Kong Zone D | 05-20 | Instance types for YiTian primary ApsaraDB RDS for MySQL instances (original ARM architecture) |
New feature | Migration of database proxies across zones | The database proxies of an RDS instance can be migrated across zones. You can migrate database proxies of your RDS instance to another zone in the region in which the RDS instance resides. | 05-16 |
April
Category | Feature | Description | Release date | References |
New feature | New version of the ApsaraDB RDS buy page | The new version of the ApsaraDB RDS buy page is supported for ApsaraDB RDS for MySQL. Compared with the old version of the ApsaraDB RDS buy page, the new version simplifies and enhances the instance purchasing process. | 04-29 | |
New feature | Cross-region backup and restoration | The cross-region backup and restoration feature is supported for RDS instances that run RDS Cluster Edition. After you enable the feature, the system automatically backs up the data of your RDS instance to another region. This feature can be used in scenarios such as regulatory compliance and disaster recovery. | 04-23 | |
New feature | Backup download | The backup file of an RDS instance that uses the ESSD storage type can be downloaded in the CSV format with headers. This helps you analyze data or archive data. In addition, the data of an RDS instance can be restored to a self-managed MySQL instance by using the backup file in the CSV or SQL format. | 04-15 | |
Feature optimization | Serverless RDS instances | The following regions and zones are supported for serverless RDS instances: Seoul Zone A Bangkok Zone A Manila Zone A Tokyo Zone A and Tokyo Zone B Kuala Lumpur Zone B Silicon Valley Zone A and Silicon Valley Zone B Virginia Zone A and Virginia Zone B London Zone A and Zone B Shanghai Zone M, Shanghai Zone N, Shanghai Zone E, Shanghai Zone G, Shanghai Zone F, Shanghai Zone B, and Shanghai Zone L Beijing Zone L, Beijing Zone I, Beijing Zone H, Beijing Zone G, and Beijing Zone K Hangzhou Zone I and Hangzhou Zone J Qingdao Zone C Zhangjiakou Zone A, Zhangjiakou Zone B, and Zhangjiakou Zone C Hohhot Zone A and Hohhot Zone B Ulanqab Zone A, Ulanqab Zone B, and Ulanqab Zone C Shenzhen Zone E and Shenzhen Zone F Heyuan Zone A and Heyuan Zone B Guangzhou Zone A and Guangzhou Zone B Chengdu Zone A and Chengdu Zone B | 04-13 |
March
Category | Feature | Description | Release date | References |
New feature | Major engine version upgrade for ApsaraDB RDS for MySQL instances that use cloud disks | The major engine version upgrade feature is supported for RDS instances that run RDS High-availability Edition or RDS Basic Edition with ESSDs. This feature allows you to upgrade the major engine version of an RDS instance from 5.7 to 8.0. This feature cannot be used to upgrade the major engine versions of read-only RDS instances. | 03-28 | |
Feature optimization | Specification change | The storage type of an RDS instance can be changed from local SSD to ESSD for better elasticity. | 03-20 | Change the storage type from local SSD to ESSD or general ESSD |
February
Category | Feature | Description | Release date | References |
Feature optimization | SSL encryption | The SSL encryption feature is supported for RDS instances that run RDS Basic Edition. | 02-26 | |
New feature | Always-confidential database | The always-confidential database feature is supported for ApsaraDB RDS for MySQL. The feature provides an encryption solution that prevents unauthorized access to your data and ensures compliance with data protection regulations. | 02-22 |
January
Category | Feature | Description | Release date | References |
Feature optimization | PITR | The point-in-time recovery (PITR) feature is supported for ApsaraDB RDS for MySQL. The PITR feature is an enhancement of the log backup feature. The PITR feature is used to restore the data of your RDS instance that uses local disks to a point in time based on the value of the Time Range of Specific Points in Time for Restoration parameter. To use the PITR feature, you must turn on Restoration to Specific Point in Time. The PITR feature resolves the issue that the restorable time range of your RDS instance is significantly shortened when the first full backup set of the RDS instance is deleted due to expiration. | 01-30 | |
Feature optimization | Enhanced SSD (ESSD) | The maximum storage capacity of an RDS instance that uses ESSDs of performance level 1 (PL1), PL2, or PL3 is changed from 32 TB to 64 TB. | 01-29 | |
New feature | New instance types for YiTian and standard RDS instances on RDS Basic Edition | Instance types that provide 1 CPU core and 1 GB of memory, 1 CPU core and 2 GB of memory, 2 CPU cores and 2 GB of memory, and 2 CPU cores and 4 GB of memory are supported for YiTian RDS instances on RDS Basic Edition. For example, your RDS instance resides in the Singapore region and uses the economy product type. If the RDS instance uses an instance type with 1 CPU core and 1 GB of memory, the monthly fee of the RDS instance is USD 3. If the RDS instance uses an instance type with 1 CPU core and 2 GB of memory, the monthly fee is USD 4. We recommend that you use the subscription billing method, which is more cost-effective. For more information, visit the ApsaraDB RDS buy page. New instance types that provide 4 cores and 8 GB of memory and 8 cores and 16 GB of memory are released for standard RDS instances on RDS Basic Edition. | 01-05 | |
New feature | Whitelist template | The whitelist template feature is supported for ApsaraDB RDS for MySQL. This feature allows you to add IP addresses to a whitelist template and associate the template with multiple RDS instances in an efficient manner. | 01-03 |
2023
December
Category | Feature | Description | Release date | References |
New feature | Binlog Cache Free Flush | The binlog cache free flush feature is supported for ApsaraDB RDS for MySQL. This feature is used to resolve the following issues during large transactions: The time that is required to process binary logs during the transaction commitment is excessively long, and your ApsaraDB RDS for MySQL instance stops responding or fails to process write requests for a long period of time. This helps improve instance stability. | 12-28 | |
New feature | Backup retention policy after instance release | The backup files of an RDS instance that uses cloud disks can be retained for a long period of time. You can specify a backup retention policy for your RDS instance, and the backup files of the RDS instance are retained for a long period of time based on the backup retention policy even if the RDS instance is released. This feature is also available for serverless RDS instances that use cloud disks. | 12-25 | |
New feature | Database proxy | The persistent connection capability is added to the database proxy feature for RDS instances that run MySQL on RDS High-availability Edition and use cloud disks. This capability ensures that your application remains connected to the database proxy of your RDS instance by using a database proxy endpoint during an instance switchover. This helps improve service availability. | 12-15 | |
New feature | Database proxy | General-purpose database proxies are provided free of charge. | 12-15 |
October
Category | Feature | Description | Release date | References |
Feature optimization | Instances that run RDS Cluster Edition | Direct node connection endpoints are supported for RDS clusters. An RDS cluster is referred to as an RDS instance that runs RDS Cluster Edition. | 10-20 | |
Feature optimization | Instances that run RDS Cluster Edition | The number of secondary nodes in an RDS cluster is increased from 4 to 8. An RDS cluster supports one primary node and up to eight secondary nodes. | 10-20 | |
Feature optimization | Serverless RDS instances | The minor engine versions of serverless ApsaraDB RDS for MySQL instances that run RDS High-availability Edition can be updated. | 10-20 | |
Feature optimization | Serverless RDS instances | The scaling range of RDS Capacity Units (RCUs) is changed from [0.5,16] to [0.5,32] for serverless RDS instances. The maximum number of RCUs is 32. | 10-18 |
September
Category | Feature | Description | Release date | References |
Feature optimization | Serverless RDS instances | RDS High-availability Edition is supported for serverless RDS instances. | 09-25 | |
Feature optimization | Serverless RDS instances | The scaling range of RCUs is changed from [0.5,8] to [0.5,16] for serverless RDS instances. The maximum number of RCUs is 16. | 09-15 |
August
Category | Feature | Description | Release date | References |
New feature | Parameter diagnostics | The parameter diagnostics feature is supported. You can use this feature to query the static parameter diagnostic results and parameter modification history within the last seven days. | 08-07 |
June
Category | Feature | Description | Release date | References |
New feature | Parameter configuration | The values of the innodb_flush_log_at_trx_commit and sync_binlog parameters can be modified. | 06-25 | Modify the innodb_flush_log_at_trx_commit and sync_binlog parameters |
April
Category | Feature | Description | Release date | References |
Feature optimization | Specification change | Manual storage reduction is supported for RDS instances that run MySQL on RDS Basic Edition or RDS High-availability Edition and use ESSDs. | 04-21 | Reduce the storage capacity of an RDS instance that uses ESSDs |
Feature optimization | Automatic storage expansion | The automatic storage expansion feature is supported for RDS instances that run MySQL on RDS Cluster Edition. | 04-19 | |
Feature optimization | Specification change | The architecture of an RDS instance that runs MySQL can be changed between x86 and ARM. | 04-17 | |
Feature optimization | Instances that run RDS Cluster Edition | RDS Cluster Edition is supported for RDS instances that run MySQL 5.7 or MySQL 8.0. An RDS cluster consists of one primary node and up to four secondary nodes to achieve high availability. Secondary nodes are readable. An RDS cluster is referred to as an RDS instance that runs RDS Cluster Edition. | 04-14 | |
Feature optimization | Data replication mode | The MySQL group replication (MGR) mode is supported for RDS instances that run MySQL on RDS Cluster Edition. | 04-14 | |
Feature optimization | RDS edition upgrade | The RDS instance that runs MySQL 8.0 or MySQL 5.7 and uses ESSDs can be upgraded from RDS High-availability Edition to RDS Cluster Edition. | 04-14 | Upgrade the RDS edition from RDS High-availability Edition to RDS Cluster Edition |
New feature | ARM architecture | The ARM architecture can be selected when you create an RDS instance. | 04-03 |
March
Category | Feature | Description | Release date | References |
Feature optimization | High-frequency physical backup | The high-frequency physical backup feature is supported for RDS instances that run MySQL 8.0 on RDS High-availability Edition and uses local disks. This feature allows you to back up your RDS instance at a high frequency. | 03-29 | Use the high-frequency physical backup feature of an RDS instance |
Feature optimization | Instance creation | A port can be specified for an RDS instance when you create the RDS instance. | 03-16 |
February
Category | Feature | Description | Release date | References |
New feature | Restoration of individual databases and tables | The fast restoration feature for individual databases and tables is supported for RDS instances that run MySQL and use cloud disks. You can restore individual databases or tables to the original RDS instance by backup set or point in time. This helps you quickly restore or analyze data. | 02-15 | |
New feature | New performance insight | The Performance Schema feature of MySQL is used to collect statistics on SQL statements to help you evaluate instance loads and identify the root causes of performance issues. The new performance insight feature also provides solutions to resolve the issues. This increases the stability of your database system. | 02-07 |
January
Category | Feature | Description | Release date | References |
Feature optimization | Monitoring and alerting | Diagnostic views for common issues are provided in addition to the classic view. You can quickly identify the causes of issues based on the trend charts of monitoring items that are displayed in these diagnostic views. | 01-13 | |
New feature | Parameter configuration | The parameters that specify the maximum number of connections to an RDS instance with cloud disks can be modified. The parameters include max_user_connections and max_connections. | 01-03 | Modify the parameters that specify the maximum number of connections to an RDS instance |
New feature | Task Center | Task Center is supported. After you perform operations on your RDS instance, you can view the task progress and historical task details on the Task Center page in the ApsaraDB RDS console. You can also change the switching time for specific tasks on the Task Center page. | 01-03 |