Deletion protection prevents a pay-as-you-go RDS instance from being manually deleted through the console or an API call. Enable it on instances running critical workloads to guard against accidental deletion caused by unintended operations or miscommunication between team members.
Deletion protection only blocks manual deletion. It does not prevent automatic release in the following cases:
-
Your account has an overdue payment for more than 15 days.
-
The instance does not comply with applicable security compliance policies.
Prerequisites
Before you begin, ensure that you have:
-
A pay-as-you-go RDS instance
How deletion protection works
When deletion protection is enabled, any attempt to delete the instance is blocked:
-
Console: an error message appears indicating the instance cannot be deleted.
-
API: the DeleteDBInstance operation returns an error.
Enable deletion protection
Enable deletion protection on an existing instance
Use either of the following methods. Both take effect immediately.
Method 1: From the Instances list
-
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 instance resides.
-
Find the instance, and choose More > Change Release Protection Settings in the Actions column.
-
In the dialog box, turn on Release Protection.
-
Click OK.
Method 2: From the instance details page
-
Go to the Instances page. Select the region, find the instance, and click its ID.
-
In the Configuration Information section of the Basic Information page, click Settings to the right of Release Protection.
-
In the dialog box, turn on Release Protection.
-
Click OK.
To enable deletion protection via API, call the ModifyDBInstanceDeletionProtection operation.
Enable deletion protection when creating an instance
To enable deletion protection during instance creation:
-
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances.
-
Click Create Instance.
-
Set Billing Method to Pay-as-you-go.
-
In the More section, select Prevents instances from being unexpectedly deleted by using the console or calling an API operation.
-
Configure the remaining parameters and complete the purchase.
For the full list of creation parameters, see Create an ApsaraDB RDS for PostgreSQL instance.
When calling CreateDBInstance or CloneDBInstance to create an instance, set the DeletionProtection parameter to enable or disable deletion protection.
Disable deletion protection
Before you can delete a protected instance, disable deletion protection first.
Method 1: From the Instances list
-
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 instance resides.
-
Find the instance, and choose More > Change Release Protection Settings in the Actions column.
-
In the dialog box, turn off Release Protection.
-
Click OK.
Method 2: From the instance details page
-
Go to the Instances page. Select the region, find the instance, and click its ID.
-
In the Configuration Information section of the Basic Information page, click Settings to the right of Release Protection.
-
In the dialog box, turn off Release Protection.
-
Click OK.
API reference
| API | Description |
|---|---|
| CreateDBInstance | Creates an instance. Use the DeletionProtection parameter to configure deletion protection at creation time. |
| CloneDBInstance | Restores an instance to a new instance. Use the DeletionProtection parameter to configure deletion protection. |
| ModifyDBInstanceDeletionProtection | Enables or disables deletion protection for an existing instance. |
What's next
-
Release or unsubscribe from an ApsaraDB RDS for PostgreSQL instance: If an instance has deletion protection enabled and you want to delete it, disable deletion protection first using the steps above.