The subscription billing method is a billing method that requires you to pay before you use resources. This billing method is suitable for scenarios with stable business traffic. Before you use the subscription billing method, you must estimate the number of resources that are required for your business. You can subscribe to the required resources for a period ranging from one month to multiple years. You must pay the subscription fees in a one-off manner. After you place an order and complete the payment, the system allocates resources to your account. If you do not renew a resource after the resource expires, the resource is reclaimed by the system.
Billable items
The following table describes the billable items of ApsaraMQ for Kafka instances that are billed based on the subscription billing method.
Billable item | Description |
Public traffic | Public traffic is divided into read traffic and write traffic. The maximum read traffic and the maximum write traffic that are supported by ApsaraMQ for Kafka are the same. When you purchase an ApsaraMQ for Kafka instance, compare the peak values of the read and write traffic of your business to determine the higher value. Then, select a traffic specification based on the higher value. You are charged for this billable item only if your instance is of the Internet- and virtual private cloud (VPC)-connected type. |
Traffic specification |
|
Disk capacity |
|
Partitions |
Note ApsaraMQ for Kafka no longer allows you to purchase instances based on the topic specification. If you purchased your existing instance based on the topic specification, the topic specification is converted into the partition specification. The number of partitions after conversion is based on the number of topics that you purchased. |
You are charged for the billable items that you use.
You can change the value of the Message Retention Period parameter to save disk space. The system deletes messages if the disk usage reaches the predetermined threshold or the retention period of messages reaches the specified value of the Message Retention Period parameter. The Message Retention Period parameter specifies the maximum period for which messages can be retained when disk capacity is sufficient. If the disk usage reaches 85%, the disk capacity is insufficient. In this case, the system deletes the earliest stored messages to ensure service availability. By default, messages are retained for up to 72 hours. You can also select a period that ranges from 24 hours to 480 hours. For more information, see When are historical messages deleted from ApsaraMQ for Kafka?
The number of API calls is not a billable item.
Billing formulas
If you use the subscription billing method for an ApsaraMQ for Kafka instance, you are charged for the billable items, such as the traffic specification and disk capacity, that you select when you create the instance. Billable items and their unit prices vary based on the instance type. For more information, see Billable items.
Internet- and VPC-connected instances: Instances of this type can be accessed over the Internet or from virtual private clouds (VPCs).
Total fees = (Unit price of Internet traffic + Price of the traffic specification + Unit price of the disk capacity × Purchased disk capacity/100 + Price of a single partition × Number of purchased partitions) × Number of months
NoteThe unit prices of Internet traffic are approximately the same as the unit prices of Elastic IP Address (EIP) traffic. If you purchase an Internet- and VPC-connected instance by topic, the total fees are calculated based on the following formula: Total fees = (Unit price of Internet traffic + Price of the traffic specification + Unit price of disk capacity × Purchased disk capacity/100 + Price of a topic × Number of additional topics) × Number of months.
VPC-connected instances: Instances of this type can be accessed only in VPCs.
Total fees = (Price of the traffic specification + Unit price of the disk capacity × Purchased disk capacity/100 + Price of a single partition × Number of purchased partitions) × Number of months
NoteIf you purchase a VPC-connected instance by topic, the total fees are calculated based on the following formula: Total fees = (Price of the traffic specification + Unit price of disk capacity × Purchased disk capacity/100 + Price of a topic × Number of additional topics) × Number of months.
Billing description
The prices and regions described in the following table are provided only for reference. The actual prices on the buy page shall prevail.
Billing of Internet traffic
Internet traffic is billed based on bandwidth. The unit prices of Internet traffic vary based on the region. The calculation results are rounded to the nearest decimal with three decimal places.
Region | Unit price of bandwidth (USD per month) | |||||
1 Mbit/s | 2 Mbit/s | 3 Mbit/s | 4 Mbit/s | 5 Mbit/s | 6 Mbit/s and higher (n indicates the bandwidth value) | |
China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), Indonesia (Jakarta), Philippines (Manila), and Thailand (Bangkok) | 3.6 | 7.2 | 11.1 | 15 | 19.6 | 19.6 + (n - 5) × 12.5 |
China (Qingdao) | 3.3 | 6.5 | 10 | 13.5 | 17.6 | 17.6 + (n - 5) × 11.3 |
Singapore, Germany (Frankfurt), Malaysia (Kuala Lumpur), US (Silicon Valley), US (Virginia), and UK (London) | 3.6 | 7.2 | 10.8 | 14.4 | 18 | 18 + (n - 5) × 12.5 |
China (Hong Kong) | 4.7 | 9.4 | 14.1 | 18.8 | 23.5 | 23.5 + (n - 5) × 15.7 |
Japan (Tokyo) and South Korea (Seoul) | 4 | 7.9 | 11.8 | 15.7 | 19.6 | 19.6 + (n - 5) × 13.2 |
Billing of traffic specifications
The billing rules of traffic specifications vary based on the instance edition. Standard Edition (High Write), Professional Edition (High Write), and Professional Edition (High Read) instances support different traffic specifications. The maximum traffic and the number of partitions in a cluster vary based on the traffic specification. The prices of traffic specifications vary based on the region group to which your region belongs. For information about region groups, see Region groups.
For information about traffic specifications supported by each instance edition, see Instance editions.
For information about traffic specifications supported by instances that are purchased based on the topic specification, see What are the number of free topics and partitions in the traffic specification of an instance that is purchased based on topic specifications?
Standard Edition (High Write)
Traffic specification | Maximum read traffic of endpoint elastic network interfaces (ENIs) (MB/s) | Maximum write traffic of ENIs (MB/s) | Number of free partitions | Unit price in region group 1 (USD per month) | Unit price in region group 2 (USD per month) | Unit price in region group 3 (USD per month) |
alikafka.hw.2xlarge | 3 × 20 | 3 × 20 | 1,000 | 250 | 370 | 340 |
alikafka.hw.3xlarge | 3 × 30 | 3 × 30 | 1,000 | 360 | 530 | 480 |
alikafka.hw.6xlarge | 3 × 60 | 3 × 60 | 1,000 | 520 | 760 | 700 |
alikafka.hw.9xlarge | 3 × 90 | 3 × 90 | 1,000 | 660 | 960 | 880 |
alikafka.hw.12xlarge | 3 × 120 | 3 × 120 | 1,000 | 800 | 1,160 | 1,070 |
Professional Edition (High Write)
Traffic specification | Maximum read traffic of ENIs (MB/s) | Maximum write traffic of ENIs (MB/s) | Number of free partitions | Unit price in region group 1 (USD per month) | Unit price in region group 2 (USD per month) | Unit price in region group 3 (USD per month) |
alikafka.hw.2xlarge | 3 × 20 | 3 × 20 | 1,000 | 600 | 870 | 800 |
alikafka.hw.3xlarge | 3 × 30 | 3 × 30 | 1,000 | 780 | 1,040 | 1,040 |
alikafka.hw.6xlarge | 3 × 60 | 3 × 60 | 1,000 | 1,130 | 1,510 | 1,510 |
alikafka.hw.9xlarge | 3 × 90 | 3 × 90 | 1,000 | 1,440 | 1,920 | 1,920 |
alikafka.hw.12xlarge | 3 × 120 | 3 × 120 | 1,000 | 1,750 | 2,330 | 2,330 |
alikafka.hw.16xlarge | 3 × 160 | 3 × 160 | 2,000 | 2,060 | 2,740 | 2,740 |
alikafka.hw.20xlarge | 3 × 200 | 3 × 200 | 2,000 | 2,980 | 3,970 | 3,970 |
alikafka.hw.25xlarge | 3 × 250 | 3 × 250 | 2,000 | 3,430 | 4,570 | 4,570 |
alikafka.hw.30xlarge | 3 × 300 | 3 × 300 | 2,000 | 3,880 | 5,170 | 5,170 |
alikafka.hw.60xlarge | 3 × 600 | 3 × 600 | 2,000 | 5,280 | 7,030 | 7,030 |
alikafka.hw.80xlarge | 3 × 800 | 3 × 800 | 2,000 | 6,220 | 8,280 | 8,280 |
alikafka.hw.100xlarge | 3 × 1,000 | 3 × 1,000 | 3,000 | 7,270 | 9,670 | 9,670 |
alikafka.hw.120xlarge | 3 × 1,200 | 3 × 1,200 | 3,000 | 8,100 | 10,780 | 10,780 |
alikafka.hw.150xlarge | 3 × 1,500 | 3 × 1,500 | 3,000 | 9,500 | 12,640 | 12,640 |
alikafka.hw.180xlarge | 3 × 1,800 | 3 × 1,800 | 3,000 | 10,910 | 14,520 | 14,520 |
alikafka.hw.200xlarge | 3 × 2,000 | 3 × 2,000 | 3,000 | 12,070 | 16,060 | 16,060 |
Professional Edition (High Read)
Traffic specification | Maximum read traffic of ENIs (MB/s) | Maximum write traffic of ENIs (MB/s) | Number of free partitions | Unit price in region group 1 (USD per month) | Unit price in region group 2 (USD per month) | Unit price in region group 3 (USD per month) |
alikafka.hr.2xlarge | 50 + 2 × 10 | 10 + 2 × 10 | 1,000 | 600 | 870 | 800 |
alikafka.hr.3xlarge | 75 + 2 × 15 | 15 + 2 × 15 | 1,000 | 780 | 1,040 | 1,040 |
alikafka.hr.6xlarge | 150 + 2 × 30 | 30 + 2 × 30 | 1,000 | 1,130 | 1,510 | 1,510 |
alikafka.hr.9xlarge | 180 + 2 × 45 | 45 + 2 × 45 | 1,000 | 1,440 | 1,920 | 1,920 |
alikafka.hr.12xlarge | 240 + 2 × 60 | 60 + 2 × 60 | 1,000 | 1,750 | 2,330 | 2,330 |
alikafka.hr.16xlarge | 240 + 2 × 80 | 80 + 2 × 80 | 2,000 | 2,060 | 2,740 | 2,740 |
alikafka.hr.20xlarge | 300 + 2 × 100 | 100 + 2 × 100 | 2,000 | 2,980 | 3,970 | 3,970 |
alikafka.hr.25xlarge | 375 + 2 × 125 | 125 + 2 × 125 | 2,000 | 3,430 | 4,570 | 4,570 |
alikafka.hr.30xlarge | 450 + 2 × 150 | 150 + 2 × 150 | 2,000 | 3,880 | 5,170 | 5,170 |
alikafka.hr.60xlarge | 900 + 2 × 300 | 300 + 2 × 300 | 2,000 | 5,280 | 7,030 | 7,030 |
alikafka.hr.80xlarge | 1,200 + 2 × 400 | 400 + 2 × 400 | 2,000 | 6,220 | 8,280 | 8,280 |
alikafka.hr.100xlarge | 1,500 + 2 × 500 | 500 + 2 × 500 | 3,000 | 7,270 | 9,670 | 9,670 |
alikafka.hr.120xlarge | 1,800 + 2 × 600 | 600 + 2 × 600 | 3,000 | 8,100 | 10,780 | 10,780 |
alikafka.hr.150xlarge | 2,250 + 2 × 750 | 750 + 2 × 750 | 3,000 | 9,500 | 12,640 | 12,640 |
alikafka.hr.180xlarge | 2,700 + 2 × 900 | 900 + 2 × 900 | 3,000 | 10,910 | 14,520 | 14,520 |
alikafka.hr.200xlarge | 3,000 + 2 × 1,000 | 1,000 + 2 × 1,000 | 3,000 | 12,070 | 16,060 | 16,060 |
Disk capacity
The billing rules of disk capacity vary based on the disk type. The unit prices of disk capacity vary based on the region group to which your region belongs. If the disk capacity provided free of charge in the traffic specification does not meet your business requirements, you can purchase additional disk capacity by increasing the value of the Disk Capacity parameter on the buy page. For information about region groups, see Region groups.
Disk type | Disk capacity (GB) | Unit price in region group 1 (USD per month) | Unit price in region group 2 (USD per month) | Unit price in region group 3 (USD per month) |
Ultra disk | 100 | 6 | 8 | 8 |
SSD | 100 | 16 | 23 | 21 |
The disk cost of a Professional Edition instance that stores data in three replicas is approximately 60% lower than the disk cost of a self-managed open source cluster.
A minimum number of disks are required to prevent issues such as rollback failures caused by frequent deletion of messages. If you want to reduce the minimum number of disks, submit a ticket.
Billing of partitions
If the number of partitions that are provided free of charge in the traffic specification does not meet your business requirements, you can purchase additional partitions by increasing the value of the Partitions parameter on the buy page. The price of each additional partition varies based on the region group. For information about region groups, see Region groups.
Billable item | Unit price in region group 1 (USD per partition-month) | Unit price in region group 2 (USD per partition-month) | Unit price in region group 3 (USD per partition-month) |
Number of partitions | 0.32 | 0.46 | 0.42 |
Billing of additional topics
This billable item is applicable only for instances that are purchased by topic.
If the number of topics that are provided free of charge in the traffic specification does not meet your business requirements, you must purchase more topics by increasing the value of the Topics parameter on the topic creation page. This option is available only to instances that are purchased by topic. Each time you purchase an additional topic, the quota of partitions is increased by 16. If the number of topics on your instance reaches the upper limit that is allowed by the current traffic specification, we recommend that you select a higher traffic specification because a higher traffic specification corresponds to more topics. This helps reduce your costs. The price of each additional topic varies based on the region group. For information about region groups, see Region groups.
Billable item | Unit price in region group 1 (USD per topic-month) | Unit price in region group 2 (USD per topic-month) | Unit price in region group 3 (USD per topic-month) |
Topic | 7 | 11 | 10 |
The default number of topics indicates the minimum number of topics that are supported by an instance. The system allocates resources to the instance based on the minimum number of topics even if you specify a smaller number of topics. In this case, your costs are not reduced.
Region groups
Region group | Region |
Region group 1 | China (Hangzhou) |
China (Shanghai) | |
China (Qingdao) | |
China (Beijing) | |
China (Zhangjiakou) | |
China (Hohhot) | |
China (Ulanqab) | |
China (Shenzhen) | |
China (Heyuan) | |
China (Guangzhou) | |
China (Chengdu) | |
Region group 2 | China (Hong Kong) |
Singapore | |
Japan (Tokyo) | |
South Korea (Seoul) | |
US (Virginia) | |
US (Silicon Valley) | |
Germany (Frankfurt) | |
UK (London) | |
Region group 3 | Malaysia (Kuala Lumpur) |
Indonesia (Jakarta) | |
Philippines (Manila) | |
Thailand (Bangkok) |
References
If you have questions about your bill, you can view the billing details. For more information, see View billing details.
For information about how to renew an instance before the instance expires, see Instance renewal.
For information about how to apply for a refund after you purchase an instance, see Refund policy.
For information about frequently asked questions (FAQ) related to billing, see Billing FAQ.