This topic describes the impact of overdue payments after your ApsaraMQ for Kafka instance expires. Renew your instance in advance to avoid impacts on your business.
Consequences of overdue payments
-
If you purchase a subscription instance, the ApsaraMQ for Kafka service in your account switches to the Expired state after the instance expires. This means that you can no longer use the ApsaraMQ for Kafka service.
-
If you purchase a pay-as-you-go or Serverless instance and your account balance is insufficient to pay your bill, the ApsaraMQ for Kafka service in your account switches to the Expired state. This means that you can no longer use the ApsaraMQ for Kafka service.
-
If the payment remains overdue for 168 hours after the instance expires, the ApsaraMQ for Kafka instance is released. After the instance is released, the instance and all related data, such as topics and Groups, are cleared and deleted. The cleared data cannot be recovered. If you want to release the instance ahead of schedule, you can force delete it in the console. For more information, see Manage instance lifecycle.
To prevent service suspension from affecting your business, renew your instance before it expires. For more information about how to renew an instance, see Renew an instance.
References
For information about the console operations and the lifecycle management of an ApsaraMQ for Kafka instance, see Manage instance lifecycle.