Lists product features and documentation updates for ApsaraDB RDS for MySQL.
For information about ApsaraDB RDS kernel version updates, see ApsaraDB RDS for MySQL AliSQL Kernel Minor Version Release Notes.
2026
May
|
Category |
Feature name |
Description |
Release date |
Related documentation |
|
New |
Support for the MySQL 8.4 major version |
RDS for MySQL now supports MySQL 8.4 on Basic Edition, High-availability Edition, and Cluster Edition instances with either cloud disks or high-performance local disks. |
May 12 |
April
|
Category |
Feature name |
Description |
Release date |
Related documentation |
|
New |
Seamless specification change |
RDS for MySQL instances that use high-performance local disks now support seamless specification change. If the host has sufficient resources, you can upgrade specifications or change storage capacity in place without data migration or connection interruptions. Available for MySQL 5.7 and later. |
April 2 |
March
|
Category |
Feature name |
Description |
Release date |
Related documentation |
|
New |
HTAP row-column diversion for MySQL 5.7 instances |
You can now enable HTAP row-column diversion for RDS for MySQL 5.7 primary instances. |
March 26 |
|
|
New |
Expanded support for DuckDB-based analytic read-only instances |
You can now add DuckDB-based analytic read-only instances to the following types of primary instances:
|
March 26 |
|
|
New |
Support for DuckDB analytic primary instances on Basic Edition |
In addition to Cluster Edition, DuckDB analytic primary instances now support Basic Edition. |
March 17 |
|
|
New |
New 96-core dedicated instance types for high-performance local disks |
RDS for MySQL High-availability Edition instances that use high-performance local disks now offer three new 96-core dedicated instance types: mysql.x4.12xlarge.2 (96 cores, 384 GB), mysql.x6.12xlarge.2 (96 cores, 576 GB), and mysql.x8.12xlarge.2 (96 cores, 768 GB). These instance types are available for MySQL 5.6, 5.7, and 8.0. |
March 12 |
February
|
Category |
Feature name |
Description |
Release date |
Related documentation |
|
Enhancement |
Increased maximum storage for high-performance local disks |
The maximum storage capacity for RDS for MySQL instances that use high-performance local disks (including primary and read-only instances) has been increased from 16,000 GB to 24,000 GB. |
February 28 |
|
|
Enhancement |
Migrate from high-performance local disks to cloud disks |
You can now migrate instances from high-performance local disks to cloud disks, even with transparent data encryption (TDE) or SSL encryption enabled. |
February 24 |
January
|
Category |
Feature name |
Description |
Release date |
Related documentation |
|
New |
RDS AI Assistant (Professional Edition) |
RDS AI Assistant (Professional Edition) is now generally available, offering the following enterprise-grade capabilities:
|
January 23 |
2025
December
|
Category |
Feature |
Description |
Release date |
References |
|
New |
DuckDB analytical primary instances |
RDS for MySQL introduces DuckDB analytical primary instances. These are standalone database instances that deeply integrate the DuckDB engine into the MySQL kernel. By using columnar storage and vectorized execution, they deliver analytic query performance that is more than 100 times faster than the MySQL InnoDB engine. Columnar storage also uses compression to reduce storage costs. These instances retain all core features of RDS for MySQL and are fully compatible with the MySQL ecosystem and your existing workflows. These instances function like regular RDS for MySQL instances, providing both robust transaction support and real-time analytics to accelerate data-driven decision-making. |
December 4 |
November
|
Category |
Feature |
Description |
Release date |
References |
|
New |
Vector storage in RDS for MySQL |
RDS for MySQL now provides deeply integrated, enterprise-grade vector data processing capabilities. It natively supports vector storage and computation for up to 16,383 dimensions and includes an optimized HNSW index algorithm for high-performance retrieval. This helps you quickly build AI applications, such as knowledge base retrieval, semantic search, and recommendation systems, within the MySQL ecosystem. |
November 28 |
|
|
Enhancement |
Updated specifications for DuckDB-based analytical read-only instances |
The specifications for DuckDB-based analytical read-only instances (High-availability Edition) are updated to include new cost-effective general-purpose types and upgraded dedicated types, providing more options. |
November 1 |
October
|
Category |
Feature |
Description |
Release date |
References |
|
New |
New RDS for MySQL zone in the Malaysia (Kuala Lumpur) region |
Zone C is now available in the Malaysia (Kuala Lumpur) region. This brings the total number of zones in the region to three, enabling three-zone disaster recovery architectures to meet the needs of industries such as finance. |
October 30 |
- |
|
New |
New RDS for MySQL zone in the UAE (Dubai) region |
Zone B is now available in the UAE (Dubai) region. This brings the total number of zones in the region to two, allowing you to deploy cross-zone high-availability architectures for disaster recovery. |
October 30 |
- |
|
Enhancement |
Blue-green deployment |
The blue-green deployment feature for RDS for MySQL now supports major version upgrades from 5.6 to 5.7 and from 5.6 to 8.0, in addition to the existing 5.7 to 8.0 upgrade path. |
October 15 |
|
|
New |
Automatic HTAP query routing for RDS for MySQL |
If your business involves both high-concurrency online transaction processing (OLTP) and complex online analytical processing (OLAP) workloads, you can add a DuckDB-based analytical read-only instance to your RDS for MySQL instance. A database proxy lets you use HTAP-based automatic query routing or manual routing using hints. OLAP queries are routed to the DuckDB-based analytical read-only instance, while OLTP queries are routed to the primary instance or a regular read-only instance. This architecture efficiently manages both transactional and analytical workloads in a unified system. |
October 14 |
September
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
Increased maximum connections and IOPS for RDS for MySQL |
As of September 19, 2025 (UTC+8), the default maximum number of connections and maximum IOPS are increased for some dedicated instance types of RDS for MySQL that use Premium Local SSDs. |
September 19 |
|
|
New |
Performance burst |
Starting September 16, 2025 (UTC+8), the performance burst feature is billable. For more information, see the official billing announcement. |
September 2 |
August
|
Category |
Feature |
Description |
Release date |
References |
|
New |
New instance types and increased maximum storage for Premium Local SSDs |
To meet diverse business needs, RDS for MySQL has introduced new primary instance types that use Premium Local SSDs and increased the maximum storage capacity to 16,000 GB. |
August 27 |
|
|
New |
DuckDB-based analytical instances |
RDS for MySQL introduces DuckDB-based analytical instances. By using columnar storage and vectorized execution, these instances deliver over 100 times the performance for complex analytical queries, enabling real-time analytics on large-scale data. |
August 6 |
Add a DuckDB analytical read-only instance to an RDS for MySQL High-availability Edition instance |
|
New |
Blue-green deployment |
Blue-green deployment is a strategy that uses a redundant environment to upgrade services. It works by creating a synchronized staging environment (green) from your existing production environment (blue) for testing and canary validation. You can quickly switch between the production and staging environments without any application changes. This minimizes service downtime and enables fast rollbacks. Important
Blue-green deployment is available only to whitelisted users. To request access, submit a ticket. You can use the feature after your application is approved. |
August 1 |
July
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
Custom password policy |
RDS for MySQL 8.0 instances now support the |
July 25 |
|
|
New |
Global Active Database (GAD) |
RDS for MySQL now supports Global Active Database (GAD). Built on RDS and Data Transmission Service (DTS), GAD provides a cost-effective, all-in-one solution for disaster recovery and multi-active database deployments. |
July 9 |
June
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
Improved SLA for multi-zone deployments |
The service level agreement (SLA) for High-availability Edition and Cluster Edition instances in multi-zone deployments increases to 99.995% for dual-zone deployments and 99.997% for deployments across three or more zones. |
June 15 |
[Product change] SLA for multi-zone RDS instances is improved |
May
|
Category |
Feature |
Description |
Release date |
References |
|
New |
New specification for Standard Edition primary instances |
A 128-core, 512 GB specification (mysql.x4.16xlarge.2c) is now available for RDS for MySQL Standard Edition primary instances on High-availability Edition with cloud disks. |
May 29 |
RDS for MySQL Standard Edition (formerly x86) primary instance specifications |
|
New |
New specification for Standard Edition read-only instances |
A 128-core, 512 GB specification (mysqlro.x4.16xlarge.1c) is now available for RDS for MySQL Standard Edition read-only instances on High-availability Edition with cloud disks. |
May 15 |
RDS for MySQL Standard Edition (formerly x86) read-only instance specifications |
|
Enhancement |
Upgrade from High-availability Edition to Cluster Edition |
The database proxy configuration is now retained when you upgrade an instance from High-availability Edition to Cluster Edition. |
May 12 |
April
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
Maximum storage for Premium Local SSDs |
The maximum storage capacity for all RDS for MySQL instances that use Premium Local SSDs, including primary and read-only instances, is increased to 16,000 GB to meet storage scaling needs. |
April 15 |
|
|
New |
Instant Add Column |
The Instant Add Column feature for RDS for MySQL optimizes |
April 14 |
February
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
SSL encryption |
RDS for MySQL 8.0 now supports mandatory SSL encryption, which is compatible with direct MySQL connections. |
February 25 |
|
|
New |
Storage compression |
RDS for MySQL instances that use ESSDs or Premium Local SSDs now support storage compression. Data is compressed at the storage layer, reducing storage costs per unit of capacity. |
February 25 |
|
|
New |
Consistency levels for read/write splitting in the database proxy |
The database proxy for RDS for MySQL offers three consistency levels in read/write splitting mode: eventual consistency, session consistency, and global consistency. |
February 24 |
|
|
Enhancement |
Maximum storage of 8,000 GB for RDS for MySQL High-availability Edition instances with Premium Local SSDs |
The maximum storage capacity has been increased from 6,000 GB to 8,000 GB for RDS for MySQL High-availability Edition instances (including primary and read-only) that have 32 cores or more and use Premium Local SSDs. |
February 21 |
January
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
Disk encryption |
You can now enable disk encryption on existing RDS for MySQL instances. Previously, disk encryption could only be enabled during instance creation. |
January 17 |
|
|
Enhancement |
SSL encryption |
RDS for MySQL 5.7 now supports mandatory SSL encryption, which is compatible with direct MySQL connections. |
January 8 |
2024
December
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhanced |
Disk encryption |
ApsaraDB RDS for MySQL Basic Edition general-purpose instances now support disk encryption at no additional cost. Enable it during instance creation to encrypt all data on the data disk at the block level. |
December 18 |
|
|
New |
RDS native replication |
RDS native replication introduces a new, cost-effective instance type for ApsaraDB RDS for MySQL. These instances leverage multi-level kernel and control plane capabilities to provide network and permission compatibility, and you can use native MySQL replication commands to manage their replication topology. |
December 6 |
|
|
New |
16KB atomic write |
Enabling 16KB atomic write ensures each data page write is atomic, allowing you to safely disable the InnoDB doublewrite mechanism. This reduces I/O writes, simplifies dirty page flushing, and significantly lowers the IOPS and bandwidth required for disk writes, which improves instance write performance. |
December 3 |
November
|
Type |
Feature |
Description |
Release date |
Documentation |
|
Enhancement |
Increased maximum IOPS for ApsaraDB RDS for MySQL high-performance local disk instances |
The maximum IOPS for ApsaraDB RDS for MySQL high-performance local disk instances, including both primary and read-only instances, has been increased to 150,000. This enhancement is available at no additional cost. |
November 29 |
|
|
New Feature |
Setting a minimum number of reserved instances in the database proxy |
Setting a minimum number of reserved instances ensures that a specific number of read-only nodes remain available to handle read requests in the event of a primary node failure or replication interruption. |
November 26 |
|
|
Enhancement |
Key rotation for encrypted cloud disks |
ApsaraDB RDS for MySQL instances with dedicated specifications now support key rotation for encrypted cloud disks. |
November 22 |
|
|
New Feature |
TDE now available for high-availability cloud disk instances |
Transparent Data Encryption (TDE) is now available on ApsaraDB RDS for MySQL high-availability cloud disk instances. TDE provides real-time I/O encryption and decryption for data files. |
November 14 |
October
|
Category |
Feature |
Description |
Release date |
References |
|
New |
Cross-availability zone deployment and nearest access for the ApsaraDB RDS for MySQL database proxy |
The database proxy for ApsaraDB RDS for MySQL now supports cross-availability zone deployment and the nearest access feature. You can deploy applications, proxy nodes, and read-only nodes in the same availability zone to minimize latency. |
October 22 |
|
|
New |
New instance types for Standard Edition primary instances |
Two new primary instance types are now available for ApsaraDB RDS for MySQL Standard Edition (formerly x86) Cluster Edition: 64-core 128 GB (mysql.x2.8xlarge.xc) and 64-core 256 GB (mysql.x4.8xlarge.xc). |
October 18 |
ApsaraDB RDS for MySQL Standard Edition (formerly x86) primary instance types |
September
|
Category |
Feature |
Description |
Release date |
References |
|
New |
database and table restoration |
Database and table restoration is now available for ApsaraDB RDS for MySQL Cluster Edition instances, enabling quick recovery from operational errors or historical data analysis. |
September 14 |
|
|
Enhancement |
column encryption |
In addition to using SQL, you can now configure column encryption rules and related user role permissions for ApsaraDB RDS for MySQL in the console. |
September 13 |
|
|
Enhancement |
database version upgrade |
You can now upgrade ApsaraDB RDS for MySQL Cluster Edition and High-availability Edition instances, including those with read-only instances, from MySQL 5.7 to 8.0. |
September 1 |
August
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
Add nodes to a cluster |
When adding a node to an RDS Cluster Edition instance, you can now select an instance type different from that of the primary instance. |
08-30 |
|
|
New |
database proxy |
Database proxy versions 2.9.1 and later now support configuring a connection pool and latency threshold for read-only endpoints. |
08-29 |
|
|
New |
database proxy |
You can now enable the database proxy feature on the purchase page. |
08-13 |
|
|
New |
database proxy |
As of August 1, 2024, database proxy version 2.9.1 now supports persistent connections during a failover to reduce connection interruptions and enhance reliability. |
08-01 |
July
|
Category |
Feature |
Description |
Release date |
References |
|
Enhancement |
performance auto-scaling |
The performance auto-scaling feature for RDS MySQL now supports General-purpose instances of High-availability Edition with high-performance local disks. This allows instances using either cloud disks or high-performance local disks to automatically scale their compute specifications (CPU and memory), scaling up to handle traffic peaks and down as traffic decreases to save resources. |
July 5 |
|
|
New |
SSL with a custom certificate |
SSL encryption secures data in transit between an RDS MySQL instance and a client, preventing it from being monitored, intercepted, or tampered with. When you configure SSL encryption for ApsaraDB for RDS for MySQL, you can now use a custom certificate as well as the cloud certificate. |
July 2 |
June
|
Category |
Feature |
Description |
Release date |
Related documents |
|
New |
Zero-ETL |
ApsaraDB RDS provides the Zero-ETL feature to synchronize data to a data warehouse, such as AnalyticDB for MySQL or ClickHouse. This eliminates data pipeline setup and maintenance. This free feature reduces data transfer costs and operational overhead. |
June 30 |
|
|
New |
Yitian Edition |
|
June 30 |
|
|
New |
Connection persistence |
The database proxy for ApsaraDB RDS for MySQL Cluster Edition instances now supports connection persistence. |
June 27 |
|
|
New |
Read-only instances |
ApsaraDB RDS for MySQL now offers Standard Edition read-only instances for its Basic Edition. To reduce the load on your database, you can create one or more read-only instances to handle high read traffic and increase application throughput. |
June 20 |
[New Feature] ApsaraDB RDS for MySQL introduces Basic Edition read-only instances on June 20, 2024 |
|
New |
MySQL major version upgrade |
A pre-check feature is now available for MySQL major version upgrades. |
June 20 |
|
|
New |
High-performance cloud disk |
A high-performance cloud disk is a new storage type for ApsaraDB RDS that is fully compatible with all features of ESSD cloud disks. It also supports I/O burst, Buffer Pool Extension (BPE), and data archiving to Object Storage Service (OSS). |
June 20 |
|
|
New |
Serverless |
You can now convert instances with high-performance cloud disks between the pay-as-you-go and Serverless billing models. |
June 06 |
|
|
New |
Serverless |
Serverless instances now support disk encryption. |
June 06 |
|
|
Optimized |
MySQL major version upgrade |
The SSL logical check is no longer required for MySQL major version upgrades. |
June 03 |
Upgrade the major version of an ApsaraDB RDS for MySQL instance |
May
|
Category |
Feature |
Description |
Release date |
Related documents |
|
New |
RDS for MySQL 5.7 supports Yitian Edition |
Yitian Edition runs on Alibaba Cloud's proprietary Yitian ARM-based chips and provides highly cost-effective instance types, enabling you to create database instances quickly and reduce IT costs. |
May 29 |
|
|
New |
Expanded availability for Yitian Edition |
RDS for MySQL Yitian Edition is available in a new availability zone: Zone D in the China (Hong Kong) region. |
May 20 |
RDS for MySQL Yitian Edition (formerly ARM) primary instance type list |
|
New |
Migrate proxy availability zone |
You can now migrate the database proxy for an RDS for MySQL instance to another availability zone within the same region. |
May 16 |
April
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
New |
New purchase page |
RDS for MySQL introduces a new purchase page with a simpler, more convenient user experience. |
04-29 |
|
|
New |
Cross-region backup and restore |
RDS for MySQL Cluster Edition instances now support cross-region backup and restore. Once enabled, data is automatically backed up to another region for regulatory compliance or disaster recovery. |
04-23 |
|
|
New |
Download backups |
You can now download backup files in CSV format with headers from RDS for MySQL ESSD-based instances for data analysis or offline archiving. Downloaded CSV or SQL backup files can be restored to a self-managed MySQL database. |
04-15 |
|
|
Optimization |
Serverless instance |
RDS for MySQL Serverless instances are now available in additional regions and availability zones: Korea (Seoul) Zone A Thailand (Bangkok) Zone A Philippines (Manila) Zone A Japan (Tokyo) Zone A, Zone B Malaysia (Kuala Lumpur) Zone B US (Silicon Valley) Zone A, Zone B US (Virginia) Zone A, Zone B UK (London) Zone A, Zone B China (Shanghai) Zone M, Zone N, Zone E, Zone G, Zone F, Zone B, Zone L China (Beijing) Zone L, Zone I, Zone H, Zone G, Zone K China (Hangzhou) Zone J, Zone K China (Qingdao) Zone C China (Zhangjiakou) Zone A, Zone B, Zone C China (Hohhot) Zone A, Zone B China (Ulanqab) Zone A, Zone B, Zone C China (Shenzhen) Zone E, Zone F China (Heyuan) Zone A, Zone B China (Guangzhou) Zone A, Zone B China (Chengdu) Zone A, Zone B |
04-13 |
March
|
Category |
Feature name |
Description |
Release date |
Related documents |
|
New |
Major version upgrade for cloud disk instances |
You can now upgrade RDS MySQL Basic Edition and High-availability Edition instances that use ESSD cloud disks from version 5.7 to 8.0, excluding read-only instances. |
March 28 |
|
|
Enhancement |
Modify Configuration |
You can now change the storage type of an RDS MySQL instance from a high-performance local disk to an ESSD cloud disk for greater elasticity. |
March 20 |
Feb
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Optimization |
SSL encryption |
RDS MySQL basic edition instances support SSL encryption. |
02-26 |
|
|
New |
fully encrypted database |
RDS MySQL now supports fully encrypted databases, protecting data from unauthorized access and helping meet data protection regulations. |
02-22 |
January
|
Category |
Feature |
Description |
Release date |
References |
|
Optimization |
Point-in-time recovery policy |
RDS for MySQL supports point-in-time recovery (PITR), an upgrade to the previous log backup feature. Enable the Point-in-time Restore switch and set the Time Range of Restoration Points. You can then restore data to any point in time within the specified number of days. This prevents the recovery time range from being significantly shortened when the earliest full backup set expires and is deleted. |
Jan 30 |
|
|
Optimization |
ESSD cloud disks |
The maximum storage capacity for RDS for MySQL ESSD cloud disks (PL1, PL2, and PL3) is increased from 32 TB to 64 TB. |
Jan 29 |
|
|
New |
New Yitian Edition and Standard Edition instance types for Basic Edition instances |
RDS for MySQL Basic Edition now offers Yitian Edition instance types with 1-core 1 GB, 1-core 2 GB, 2-core 2 GB, and 2-core 4 GB specifications. For example, in the Singapore region, the monthly compute price for the new 1-core 1 GB and 1-core 2 GB RDS for MySQL instances is only $3 and $4, respectively. An annual subscription is more cost-effective. Buy now RDS for MySQL Basic Edition also adds Standard Edition instance types with 4-core 8 GB and 8-core 16 GB specifications. |
Jan 05 |
|
|
New |
Whitelist templates |
RDS for MySQL adds whitelist templates. Configure rules in an IP whitelist template and quickly apply them to multiple RDS for MySQL instances. |
Jan 03 |
2023
December
|
Category |
Feature |
Description |
Release date |
References |
|
New |
Binlog Cache Free Flush |
ApsaraDB RDS for MySQL now supports Binlog Cache Free Flush, which improves instance stability by resolving issues during large transaction commits, such as excessive binlog write times, instances becoming unwritable, or instance hangs. |
December 28 |
|
|
New |
Backup retention after instance release |
Cloud disk instances of ApsaraDB RDS for MySQL, including serverless instances, now support long-term backup retention. You can configure a backup retention policy to keep backup files even after an instance is released. |
December 25 |
|
|
New |
Persistent connections for the database proxy |
The database proxy now supports persistent connections on High-availability Edition cloud disk instances of ApsaraDB RDS for MySQL. Application connections to the proxy stay active during an instance switchover, improving service availability. |
December 15 |
|
|
New |
General-purpose database proxy |
ApsaraDB RDS for MySQL now offers a general-purpose database proxy at no additional cost. |
December 15 |
October
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
Cluster Edition instances |
RDS for MySQL Cluster Edition instances now support direct connection endpoints for each cluster node. |
October 20 |
View and manage the endpoints and port numbers of an ApsaraDB RDS for MySQL instance |
|
Enhancement |
Cluster Edition instances |
The maximum number of secondary nodes for RDS for MySQL Cluster Edition instances has increased from 4 to 8, allowing for a configuration of 1 primary and 8 secondary nodes. |
October 20 |
|
|
Enhancement |
Serverless instances |
You can now upgrade the minor engine version of High-availability Edition RDS for MySQL Serverless instances. |
October 20 |
Upgrade the minor engine version of an ApsaraDB RDS for MySQL instance |
|
Enhancement |
Serverless instances |
The selectable range of RDS Capacity Units (RCUs) for RDS for MySQL Serverless instances has been expanded from [0.5, 16] to [0.5, 32]. |
October 18 |
September
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
serverless instance |
RDS MySQL serverless instances support high availability. |
September 25 |
|
|
Enhancement |
serverless instance |
The configurable range of RDS Capacity Units (RCUs) for RDS MySQL serverless instances has been expanded from [0.5, 8] to [0.5, 16]. |
September 15 |
August
|
Category |
Feature |
Description |
Release date |
Documentation |
|
New |
Parameter Diagnosis |
You can now diagnose the parameters of your database instance, view static diagnostic results, and review the parameter modification history for the last 7 days. |
August 7 |
June
|
Category |
Feature |
Description |
Release date |
References |
|
New |
Configure instance parameters |
RDS for MySQL now supports modifying the innodb_flush_log_at_trx_commit and sync_binlog parameters. |
June 25 |
Adjust the innodb_flush_log_at_trx_commit and sync_binlog parameters |
April
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
Change configuration |
RDS MySQL Basic Edition and High-availability Edition instances that use ESSD cloud disks support manual disk space scale-down. |
04-21 |
|
|
Enhancement |
Automatic storage expansion |
RDS MySQL Cluster Edition instances support automatic storage expansion. |
04-19 |
|
|
Enhancement |
Change configuration |
You can now change the compute architecture of RDS MySQL instances from x86 to ARM, and vice versa. |
04-17 |
|
|
Enhancement |
Cluster Edition instances |
RDS MySQL 5.7 and 8.0 support Cluster Edition. This edition provides a high-availability deployment with one primary node and up to four readable secondary nodes. |
04-14 |
|
|
Enhancement |
Replication method |
RDS MySQL Cluster Edition instances support Group Replication (MGR). |
04-14 |
|
|
Enhancement |
Edition upgrade |
You can upgrade RDS MySQL 8.0 and 5.7 High-availability Edition instances on ESSD cloud disks to Cluster Edition. |
04-14 |
Upgrade a High-availability Edition instance to a Cluster Edition instance |
|
New |
ARM-based instance |
You can create ARM-based RDS MySQL instances. |
04-03 |
March
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
high-frequency physical backup |
RDS for MySQL 8.0 high availability instances with high-performance local disks now support high-frequency physical backup. |
March 29 |
|
|
Enhancement |
create instance |
You can now specify the instance port when you create an RDS instance. |
March 16 |
February
|
Category |
Feature |
Description |
Release date |
Related documents |
|
New |
Database and table recovery |
RDS MySQL cloud disk instances now support fast database and table recovery. Restore specific databases or tables to the original instance by using a backup set or performing point-in-time recovery to quickly recover from operational errors or analyze historical data. |
02-15 |
|
|
New |
Performance Insight (New Version) |
Performance Insight (New Version) uses MySQL's |
02-07 |
January
|
Category |
Feature |
Description |
Release date |
Related documentation |
|
Enhancement |
monitoring and alerting |
In addition to the Classic View, diagnostic views for common issues are now available. These views let you analyze trends in key metrics to quickly identify root causes. |
01-13 |
|
|
New |
Set instance parameters |
You can now modify the |
01-03 |
|
|
New |
Task Center |
The Task Center is now available. After performing an operation on an instance, use the Task Center to view the progress of current tasks, review historical task details, and change the execution time for some switchover tasks. |
01-03 |