Operation Stage | Protection Mechanism | Mechanism Description | Reference Document |
Protection before deletion | Termination protection | After enabling instance termination protection, the instance will no longer be accessible via the console or API. If you need to terminate the instance, you must manually disable termination protection before executing the destruction operation. It is recommended to keep this protection enabled for key business operations long-term. Instance termination protection does not take effect at the system level, such as hourly billed instances being released due to overdue payment or annual and monthly subscription instances being released after isolation upon expiration. | |
Verify when deleting | MFA authentication | MFA (Multi-Factor Authentication) is a simple and effective security authentication method. It can add an extra layer of protection outside username and password. CKafka has enabled MFA authentication by default for instance deletion. To delete an instance, you must first complete the authentication process (WeChat Scan Code Verification or verify with verification code on cell phone) to ensure it is performed by yourself. | - |
Buffer after deletion | Isolation period retention | After an annual and monthly subscription instance is deleted, it will be retained on the console for 7 days with a status display of isolated. Instances in an isolated state cannot produce or consume data. Data stored in CKafka and configuration will not be terminated. Expired messages will still be automatically deleted following the open-source Kafka mechanism. During this period, you can manually renew the instance. After the renewal is successful, the instance can be resumed to normal operating status and can be used normally. Pay-as-you-go instances cannot be restored after deletion. Proceed with caution. |
Feedback