Involved instance types

All instance types that are supported for ApsaraDB RDS for MySQL instances on RDS Enterprise Edition

Effective date

August 31, 2023

Impacts

The end of sale (EOS) or discontinuation has the following impacts on existing and new RDS instances:

• Existing RDS instances:

  • The services for existing RDS instances that run RDS Enterprise Edition are not affected. You can seek after-sales services and submit tickets as normal.

  • Most of the features of existing RDS instances that run RDS Enterprise Edition are not affected. For example, you can still change the specifications or renew an existing RDS instance. However, you cannot perform the following operations:

    • Upgrade an RDS instance from RDS High-availability Edition to RDS Enterprise Edition.

    • Restore and rebuild an RDS instance after it is released. For more information, see Manage ApsaraDB RDS for MySQL instances in the recycle bin.

    • Restore data of an RDS instance from backup files to a new RDS instance. For more information, see Restore full data of an ApsaraDB RDS for MySQL instance.

      Note

      If you want to restore data, you can use other restoration features, such as data restoration from a logical backup of Data Disaster Recovery to the original RDS instance and data tracking in DMS. For more information, see Restore a MySQL database from a logical backup and Data tracking.

• New RDS instances: You can no longer select RDS Enterprise Edition when you create an RDS instance.

Suggestions

• Existing RDS instances: To ensure business stability, we recommend that you upgrade your RDS instance from RDS Enterprise Edition to RDS Cluster Edition. In RDS Cluster Edition, one primary node and two secondary nodes are provisioned by default. For more information data migration methods, see Migrate data from an ApsaraDB RDS for MySQL Enterprise Edition instance to an ApsaraDB RDS for MySQL Cluster Edition instance.

  Note

  RDS Cluster Edition for ApsaraDB RDS for MySQL provides all features that are provided by RDS Enterprise Edition. RDS Cluster Edition also provides the following features: automatic failover, primary/secondary switchover, readable secondary nodes, node addition and deletion, node-level monitoring, and cluster topology management. RDS Cluster Edition also supports the MySQL group replication (MGR) mode and ensures a zero recovery point objective (RPO). RDS Cluster Edition is more cost-efficient, flexible, and stable than RDS Enterprise Edition.

  For more information about the features that are supported by RDS Cluster Edition and feature configuration, see RDS Cluster Edition and Add a node to an ApsaraDB RDS for MySQL cluster.

  The following table compares RDS Cluster Edition and RDS Enterprise Edition.

  Metric	RDS Enterprise Edition	RDS Cluster Edition
  Number of nodes or instances	3	2 to 5
  Readable instances or nodes	No	Yes
  Endpoint type	Read/write endpoint	Read/write endpoint: This type of endpoint is used to connect to the primary node in an ApsaraDB RDS for MySQL cluster to process read and write requests. Read-only endpoint: This type of endpoint is used to connect to the secondary nodes in an ApsaraDB RDS for MySQL cluster to process read requests.
  Replication mode	Multi-replica synchronous replication	Asynchronous replication, semi-synchronous replication, and MGR
  Maximum number of unavailable instances or nodes that can be accepted	1	n - 1. n indicates the number of nodes in an ApsaraDB RDS for MySQL cluster.
  Number of zones	Less than or equal to 3	Less than or equal to the number of nodes in an ApsaraDB RDS for MySQL cluster.

• New RDS instances: We recommend that you select RDS Cluster Edition when you create an RDS instance.