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.
Release notes in 2024
February
Category | Feature | Description | Date | References |
Feature optimization | SSL encryption | The SSL encryption feature is supported for ApsaraDB RDS for MySQL instances that run RDS Basic Edition. | 02-26 | |
New feature | Always-confidential database | The always-confidential 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 | 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 | ESSD | The maximum storage capacity of an RDS instance that uses enhanced SSDs (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 economy and standard RDS instances on RDS Basic Edition | New instance types that provide 1 core and 1 GB of memory, 1 core and 2 GB of memory, 2 cores and 2 GB of memory, and 2 cores and 4 GB of memory are released for economy 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 |
Release notes in 2023
December
Category | Feature | Description | 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 | 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 | 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 | 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 | Date | References |
New feature | Instance 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 | 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 cloud disks |
Feature optimization | Automatic storage expansion | Automatic storage expansion 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 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 | 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 | |
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 | 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 | 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 | Instance 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 specify and change the switching time of your workloads for specific tasks on the Task Center page. | 01-03 |