This topic describes how to release a pay-as-you-go ApsaraDB RDS for MySQL instance and how to unsubscribe from a subscription ApsaraDB RDS for MySQL instance.

Precautions

  • After you release or unsubscribe from an RDS instance, the RDS instance and its data are immediately deleted. Before you release or unsubscribe from an RDS instance, we recommend that you back up the RDS instance and download the required backup files. For more information, see Enable automatic backups for an ApsaraDB RDS for MySQL instance and Download the backup files of an ApsaraDB RDS for MySQL instance.
    Note
    • If an RDS instance runs the RDS Basic Edition or High-availability Edition with standard SSDs or enhanced SSDs (ESSDs), you cannot download the backup files of the RDS instance.
    • If an RDS instance is equipped with local SSDs, you can use the Backup Retention Policy After Release parameter in the ApsaraDB RDS console to specify which backup files you want to retain after you release or unsubscribe from the RDS instance. This way, after you release or unsubscribe from the RDS instance, the data backup files of the RDS instance are not deleted. You can download the data backup files to your computer. For more information, see Retain data backup files after instance release.
  • If you release or unsubscribe from the last read-only RDS instance of a primary RDS instance, you must disable the read/write splitting feature for the primary RDS instance. For more information, see Disable read/write splitting for an RDS MySQL instance.
  • After you release or unsubscribe from an RDS instance, ApsaraDB RDS moves the RDS instance to the recycle bin if the RDS instance meets specific requirements. For more information, see Manage ApsaraDB RDS for MySQL instances in the recycle bin
  • After you release or unsubscribe from a primary RDS instance, the subscription read-only RDS instances and pay-as-you-go read-only RDS instances of the primary RDS instance are automatically deleted. In addition, the payments for the subscription read-only RDS instances of the primary RDS instance are refunded.

Release a pay-as-you-go RDS instance

  1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where the RDS instance resides.
  2. Use one of the following methods to open the Release Instance message:
    • Find the RDS instance. In the Actions column, choose More > Release Instance.
      1. Find the RDS instance and click the instance ID.
      2. On the Basic Information page, click Release Instance.
  3. In the message that appears, click Confirm.

Unsubscribe from a subscription RDS instance

If you want to unsubscribe from an RDS instance, submit a ticket.

FAQ

  • If I release or unsubscribe from a read-only RDS instance, are my workloads interrupted?
    Yes, if you release or unsubscribe from a read-only RDS instance, your workloads on the read-only RDS instance are interrupted. Before you release or unsubscribe from a read-only RDS instance, we recommend that you set the read weight of the read-only RDS instance to 0. For more information, see Modify the latency threshold and read weights of ApsaraDB RDS for MySQL instances.
    Note The cached connections to the read-only RDS instance remain valid. If you want to route the read requests over the cached connections to the other read-only RDS instances, you must establish new connections.
  • After I release or unsubscribe from my RDS instance, how do I retrieve the data of the RDS instance?

    If your RDS instance is configured to retain backup files after you release or unsubscribe from your RDS instance, you can go to the Backup for Deleted Instances tab of the Backups page in the ApsaraDB RDS console to restore the data of your RDS instance. For more information, see Enable automatic backups for an ApsaraDB RDS for MySQL instance.

Related operations

Operation Description
Release instance Releases a pay-as-you-go ApsaraDB RDS instance. You cannot unsubscribe from a subscription ApsaraDB RDS instance by calling an API operation.