ApsaraDB RDS for MySQL instances running RDS Enterprise Edition are no longer receiving new feature updates. Future feature development continues in PolarDB-X.
Existing RDS Enterprise Edition instances remain fully operational and continue to receive extended support, including bug fixes and long-term technical assistance.
If you are running RDS Enterprise Edition, migrate to one of the following products to access the latest features and improvements.
Migration solutions
Two migration paths are available. Both support MySQL 5.7 and MySQL 8.0.
| Solution 1: PolarDB-X 2.0 Standard Edition | Solution 2: RDS Cluster Edition | |
|---|---|---|
| Architecture | Financial-grade | High availability (HA), one primary node + up to eight secondary nodes |
| Compute-storage separation | — | Yes |
| Readable secondary nodes | — | Yes |
| Zero RPO | Yes (financial-grade disaster recovery) | Yes (MySQL Group Replication) |
| Migration method | One-click migration | Manual migration |
| Endpoint retained after migration | Yes | — |
| Region availability | Selected regions (see below) | All regions except Middle East regions |
Solution 1: Migrate to PolarDB-X 2.0 Standard Edition
PolarDB-X 2.0 Standard Edition is fully compatible with all features of RDS Enterprise Edition. It provides financial-grade disaster recovery, ensuring zero recovery point objective (RPO) and zero data loss when a data center failure occurs. PolarDB-X 2.0 Standard Edition delivers better performance and higher cost-effectiveness than native MySQL.
Migration method: Use the one-click migration feature. After migration, the original RDS instance endpoint is retained, so no changes to your application's connection settings are required.
For migration steps, see Upgrade an ApsaraDB RDS for MySQL Enterprise Edition instance to a PolarDB-X 2.0 Standard Edition instance.
PolarDB-X 2.0 Standard Edition is available in the following regions: China (Beijing), China (Hangzhou), China (Hong Kong), China (Qingdao), China (Shanghai), China (Shenzhen), China (Zhangjiakou), Germany (Frankfurt), Indonesia (Jakarta), Singapore, US (Silicon Valley), and US (Virginia). To create an instance in a region not listed here, submit a ticket.
Solution 2: Migrate to RDS Cluster Edition
RDS Cluster Edition uses a high availability (HA) architecture with one primary node and multiple readable secondary nodes, supports compute-storage separation, and is fully compatible with all features of RDS Enterprise Edition. Up to eight secondary nodes can be created. MySQL Group Replication (MGR) mode ensures zero RPO. An RDS instance running RDS Cluster Edition is called an RDS cluster.
Migration method: Manually migrate your data.
For migration steps, see Migrate data from an ApsaraDB RDS for MySQL Enterprise Edition instance to an ApsaraDB RDS for MySQL Cluster Edition instance.
RDS Cluster Edition is available in all regions except Middle East regions.