Deletion Protection
Last updated:2026-01-23 17:52:25
TDMQ for RocketMQ provides a multi-dimensional cluster deletion protection mechanism that prevents accidental deletion of clusters through the console or application programming interfaces (APIs), ensuring business data security.
Operation | Protection Mechanism | Description | Documentation |
Pre-deletion protection | Deletion protection switch | After deletion protection is enabled for a cluster, the cluster cannot be deleted through the console or using an API. To delete the cluster, you need to manually disable the deletion protection feature first. It is recommended that this feature always be enabled for key businesses. Cluster deletion protection does not apply to system-level deletion. For example, pay-as-you-go clusters are released due to overdue payment, and yearly/monthly subscription clusters are isolated and released after expiration. | |
Deletion verification | Multi-factor authentication (MFA) | MFA is a simple and effective security authentication method. It adds an extra layer of security beyond usernames and passwords. MFA is enabled by default for TDMQ for RocketMQ cluster deletion. To delete a cluster, you should complete identity verification through WeChat QR code and mobile Captcha to ensure that the deletion operation is performed by the account owner. | |
Post-deletion retention time | Isolation period retention | After a yearly/monthly subscription cluster is deleted, the cluster remains isolated for 7 days. During this period, you can manually delete the cluster permanently or restore it. After this period, the cluster is permanently deleted along with all resources and metadata, which cannot be restored. Back up your data in advance. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback