ApsaraMQ for Kafka:Subscription billing

Internet- and VPC-connected instances

An Internet- and VPC-connected instance can be accessed over both the Internet and a virtual private cloud (VPC). The total fee is calculated as follows:

Total fee = (Unit price of Internet traffic + Unit price of traffic specifications + Unit price of disk capacity × Purchased disk capacity/100 + Unit price of partitions × Number of purchased partitions) × Number of months

VPC-connected instances

A VPC-connected instance can be accessed only over a VPC. The total fee is calculated as follows:

Total fee = (Unit price of traffic specifications + Unit price of disk capacity × Purchased disk capacity/100 + Unit price of partitions × Number of purchased partitions) × Number of months

Variables in the formulas

• Unit price of Internet traffic — The monthly price of the Internet bandwidth of the instance. Take the value from Internet traffic billing.

• Unit price of traffic specifications — The monthly price of the traffic specification of the instance. Take the value from Traffic specification billing.

• Unit price of disk capacity — The monthly price of 100 GB of disk capacity. Take the value from Disk capacity billing. Because the price is quoted per 100 GB, the purchased capacity is divided by 100 in the formulas.

• Purchased disk capacity — The disk capacity in GB that you purchase in addition to the capacity that is included in your traffic specification.

• Unit price of partitions — The monthly price of one additional partition. Take the value from Partition billing.

• Number of purchased partitions — The number of partitions that you purchase in addition to the partitions that are included in your traffic specification.

• Number of months — The subscription duration in months.

Instances that are purchased based on topic specifications

If your instance is purchased based on topic specifications, replace the partition terms in the preceding formulas with topic terms:

• Internet- and VPC-connected instance: Total fee = (Unit price of Internet traffic + Unit price of traffic specifications + Unit price of disk capacity × Purchased disk capacity/100 + Unit price of topics × Number of added topics) × Number of months

• VPC-connected instance: Total fee = (Unit price of traffic specifications + Unit price of disk capacity × Purchased disk capacity/100 + Unit price of topics × Number of added topics) × Number of months

  Number of added topics is the number of topics that you add in addition to the topics that are included in your traffic specification.

Estimate verification

After you calculate an estimate, confirm the unit prices on the buy page in the console, and then compare the estimate with the actual charges in your consumption details.

Region groups

Traffic specification, disk capacity, and partition unit prices differ by region group. The following table lists the regions in each region group.

SAU (Riyadh - Partner Region) does not belong to a region group. Unit prices for this region are listed in a dedicated column in the pricing tables of this topic.

Internet traffic billing

Internet traffic of an ApsaraMQ for Kafka instance is billed based on bandwidth, and unit prices differ by region. Settlement amounts are rounded to three decimal places. The unit price of Internet traffic is essentially the same as the unit price of Elastic IP Address (EIP) traffic.

Traffic specification billing

Traffic specification fees of an ApsaraMQ for Kafka instance depend on the instance edition, the traffic specification, and the region group. Each edition supports a different set of traffic specifications, and each traffic specification defines the peak traffic for the computing capacity of the cluster and the number of pre-included partitions. Take the unit price from the table of your edition and from the column of your region group.

For more information about instance editions and specifications, see Specifications.

Not every traffic specification is offered in every region. A value of Not available in a unit price column indicates that the traffic specification is not offered in that region.

Disk capacity billing

Disk capacity fees of an ApsaraMQ for Kafka instance depend on the disk type, and unit prices differ by region group. Unit prices in the following tables apply to 100 GB of disk capacity. If the disk capacity that is included in your traffic specification does not meet your requirements, purchase additional disk capacity.

Analyze your resource requirements based on your actual business volume before you decide how much disk capacity to purchase. The capacity you need depends on the maximum message retention period: the longer messages are retained, the more disk capacity you must purchase, and the higher your disk fee.

• Messages are deleted when either the disk capacity limit or the configured retention period is reached, whichever occurs first. The maximum message retention period specifies the retention period that applies when disk space is sufficient.

• If disk usage reaches 85%, the oldest messages are deleted ahead of schedule to keep the service available.

• The default retention period is 72 hours. Valid values: 24 to 480 hours.

  For more information, see When does ApsaraMQ for Kafka delete old messages?.

Partition billing

Each traffic specification includes a number of partitions. When you purchase an ApsaraMQ for Kafka instance based on partition specifications, you can purchase additional partitions if the number of partitions that is included in the specification does not meet your requirements. For the number of partitions of each instance specification, see Specifications. The unit price of each additional partition differs by region group.