If your ApsaraDB RDS for SQL Server instance uses the pay-as-you-go billing method and runs critical workloads, you can enable the release protection feature for the instance. This feature prevents your RDS instance from being manually released due to unintended operations or lack of communication among team members. This topic describes how to enable or disable the release protection feature for an ApsaraDB RDS for SQL Server instance.

Prerequisites

The RDS instance uses the pay-as-you-go billing method.

Precautions

The release protection feature cannot prevent the automatic release of RDS instances in normal scenarios such as the following scenarios:
  • A payment in your account is overdue for more than 15 days.
  • The RDS instance does not comply with the applicable security compliance policies.

Benefits of release protection

If you release an RDS instance for which the release protection feature is enabled, the following result is returned:
  • If you release the RDS instance in the ApsaraDB RDS console, the "The instance cannot be released because release protection has been enabled. Disable release protection first" message is displayed.
  • If you call the DeleteDBInstnace operation to release the RDS instance, the error code OperationDenied.DeletionProtection is returned.

Enable the release protection feature when you create an RDS instance

This section describes how to configure the release protection feature when you create an RDS instance. For more information, see Create an ApsaraDB RDS for SQL Server 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. On the Instances page, click Create Instance.
  3. In the Basic Configurations step, set Billing Method to Pay-As-You-Go and complete the remaining configurations. Click Next: Instance Configuration.
  4. In the Instance Configurations step, select Prevent release through the console or API by mistake and complete the remaining configurations. Click Next: Confirm Order.
  5. Complete the remaining configurations until the RDS instance is created.
Note When you can call the CreateDBInsance or CloneDBInstance operation to create an RDS instance, you can enable or disable the release protection feature for the RDS instance by setting the DeletionProtection parameter.

Modify release protection settings

You can also enable or disable the release protection feature for an RDS instance by modifying the settings of the 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. On the Instances page, find the RDS instance whose release protection settings you want to modify. In the Actions column, click More and select Change Instance Release Protection Settings.
  3. In the Change Release Protection Setting dialog box, turn on or turn off Release Protection.
  4. Click OK.
Note You can also call the ModifyDBInstanceDeletionProtection operation to enable or disable the release protection feature for an RDS instance.

Check whether the release protection feature is enabled

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. On the Basic Information page, view the Release Protection section of the Configuration Information section.
    Release Protection

Related operations

Operation Description
Create an instance Creates an ApsaraDB RDS instance.
Restore data to a new ApsaraDB RDS instance Restores the data of an ApsaraDB RDS instance to a new instance. The new instance is also called a cloned instance.
Enable or disable the release protection feature Enables or disables the release protection feature for an ApsaraDB RDS instance.