Release Notes
Broker Release Notes
Announcement
Operation | Protection Mechanism | Description | Reference Documentation |
Pre-deletion protection | Deletion protection | After instance deletion protection is enabled, the instance cannot be deleted through the console or an API. To delete the instance, you need to manually disable the deletion protection feature first. It is recommended to keep this feature enabled for key businesses. Instance deletion protection does not apply to system-level deletion. For example, postpaid by hour instances are isolated and subsequently released due to overdue payment, and yearly/monthly subscription instances 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 CKafka instance deletion. To delete an instance, 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 yearly/monthly subscription instance is deleted, the instance will be retained in the console for 7 days in an isolated status. Isolated instances cannot produce or consume data, but the data and configurations stored in the CKafka instance will not be deleted. Expired messages will continue to be automatically deleted according to the Apache Kafka mechanism. During this period, you can manually renew the instance. After renewal, the instance will recover to its normal status and become fully functional. Pay-as-you-go instances cannot be recovered after deletion. Proceed with caution. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback