This topic describes the billing methods of ApsaraMQ for Kafka. You can select a billing method that meets your business requirements based on the description of this topic.
The connector feature of ApsaraMQ for Kafka depends on EventBridge. ApsaraMQ for Kafka does not charge you extra fees for the connector feature. For information about the billing rules of EventBridge, see Billing. Alibaba Cloud does not provide a service level agreement (SLA) for the connector feature. For information about the SLAs and fees of other services on which the connector feature depends, see the documentation of the related services.
Overview of billing documentation
ApsaraMQ for Kafka supports the subscription and pay-as-you-go billing methods. For information about the differences among instance editions and features, see Instance editions.
Category | References |
Subscription | |
Pay-as-you-go | |
Other related topics | Change the billing method from pay-as-you-go to subscription |
Set the notification policy for imminent overdue payments and instance release | |
Billing methods
ApsaraMQ for Kafka supports the following billing methods:
Subscription: a billing method that requires you to pay before you use resources. This billing method is suitable for scenarios with stable business traffic.
Pay-as-you-go: a billing method that allows you to pay based on your actual resource usage. In most cases, this billing method is suitable for testing or short-term use scenarios in which traffic peaks are uncertain.
You can change the billing method of an ApsaraMQ for Kafka instance only from pay-as-you-go to subscription. When you change the billing method of an instance, you cannot change the configurations of the instance. For more information, see Change the billing method from pay-as-you-go to subscription.