Operation | Protection Mechanism | Mechanism Description | Reference Documentation |
Pre-deletion protection | Deletion protection | After deletion protection is enabled for a cluster, the cluster cannot be deleted through the console or an API. To delete the cluster, you need to manually disable the deletion protection feature first. It is recommended to keep this feature enabled for key businesses. Cluster deletion protection does not apply to system-level deletion. For example, postpaid by hour clusters are isolated and subsequently 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 RabbitMQ cluster deletion. To delete a cluster, you should complete identity verification through WeChat QR code and mobile Captcha to ensure the action is authorized by the account owner. | |
Post-deletion retention period | Isolation period retention | After a 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 recovered. It is recommended to back up your data in advance. During the isolation period, message reading and writing in the cluster are prohibited, and both console operations and cloud API calls are restricted. Any saved and unconsumed messages in the cluster will be discarded. Make sure that you back up your data in advance. |
피드백