You are billed for ApsaraMQ for RabbitMQ Serverless Edition instances based on the pay-as-you-go billing method. This allows you to use ApsaraMQ for RabbitMQ resources without the need to reserve them. This topic describes the billable items and billing rules of ApsaraMQ for RabbitMQ Serverless Edition instances.
Limits
ApsaraMQ for RabbitMQ Serverless Edition instances are available only in specific regions. For more information, see Supported regions.
Billable items
Billable item | Required | Billing method | Settlement cycle |
Number of API calls initiated to receive and deliver messages | Yes | Pay-as-you-go | Hourly |
Number of queues | Yes | ||
Message storage space | Yes | ||
Outbound Internet traffic | No If the Internet access feature is not enabled, you are not charged Internet traffic fees. | ||
Message traces | No If the message trace feature is not enabled, you are not charged message trace fees. |
Number of API calls initiated to receive and deliver messages
You are charged messaging fees for an ApsaraMQ for RabbitMQ Serverless Edition instance based on the total number of API calls that are initiated to receive and deliver messages on the instance.
Billing formula
Messaging fees per hour = Total number of API calls initiated to receive and deliver messages × Unit price of API calls (USD per API call)
Rules for calculating the number of API calls initiated to receive and deliver messages
Number of API calls initiated to receive and deliver messages = Number of API calls initiated to receive messages + Number of API calls initiated to deliver messages
Number of API calls initiated to receive messages: the number of API calls that are initiated to receive messages in queues. For example, if a message that is received by an exchange is routed to three queues, three API calls are counted to receive the message.
Number of API calls initiated to deliver messages: the number of API calls that are initiated to deliver messages. Each time a message is delivered, an API call is counted, regardless of whether the message is processed or whether an acknowledgment (ACK) is returned for the message.
Payload size: When you calculate the number of API calls that are initiated to deliver a message, you must use a payload multiplier that is calculated based on a message size of 4 KB. If the size of a message is not divisible by 4, the value is rounded up to the next smallest integer. For example, if you deliver a message whose size is 18 KB, the number of API calls that are initiated to deliver the message is 5. The number of API calls is calculated by using the following formula: ⌈18/4⌉ = 5.
Note⌈ ⌉ indicates that the value is rounded up to the next smallest integer.
Unit prices
Type | Unit price by region (USD per 1 million calls) | |
Regions other than SAU (Riyadh - Partner Region) | SAU (Riyadh - Partner Region) | |
Receipt and delivery of normal messages | 0.31 | 0.372 |
Receipt of delayed messages | 1.55 | 1.86 |
Delivery of delayed messages | 0.31 | 0.372 |
Billing example
The following items describe the number of API calls initiated to receive and deliver messages on an instance that resides in the China (Hangzhou) region in a specific hour:
Seven million API calls are initiated to receive normal messages and 2 million API calls are initiated to receive delayed messages on the broker. The size of each message is 8 KB.
Eight million API calls are initiated to deliver normal messages and 3.2 million API calls are initiated to deliver delayed messages on the broker. The size of each message is 8 KB.
In this case, the messaging fee of the instance for the hour is USD 17.484. The fee is calculated by using the following formula: (7 + 8) × ⌈8/4⌉ × 0.31 + 2 × ⌈8/4⌉ × 1.55 + 3.2 × ⌈8/4⌉ × 0.31 = 17.484.
Number of queues
You are charged queue fees for queues on an ApsaraMQ for RabbitMQ Serverless Edition instance based on the number of queues.
Billing formula
Queue fees per hour = Number of queues created on the instance × Unit price of queues (USD per queue)
The system counts the largest number of created queues on an instance in an hour when calculating the queue fees of the instance.
For example, you created 300 queues on an instance and then deleted 100 queues from the instance in a specific hour. In this case, 300 queues are counted when the system calculates the queue fees.
Unit prices
The unit prices of queues are calculated based on a tiered pricing policy.
Billing tier | Unit price (USD per queue per hour) |
[0,200] | 0.000044 |
[201,3000] | 0.000022 |
[3001,20000] | 0.000044 |
[20001,100000] | 0.000088 |
Billing example
The following table describes the number of created queues on an instance in 2 hours on a specific day.
Item | Quantity | Billed quantity | Unit price | Total cost |
First hour | 150 queues are created and then 50 queues are deleted. | 150 | 150 queues fall in the [0,200] tier. The unit price is USD 0.000044 per queue per hour. | The queue fee for the hour is USD 0.0066. The fee is calculated by using the following formula: 150 × 0.000044 = 0.0066. |
Second hour | Additional 500 queues are created. | 600 |
| The queue fee for the hour is USD 0.0176. The fee is calculated by using the following formula: 200 × 0.000044 + 400 × 0.000022 = 0.0176. |
Message storage space
You are charged storage fees for an ApsaraMQ for RabbitMQ Serverless Edition instance based on the storage space that messages occupy and the storage duration of messages on the broker.
Billing formula
Storage fees per hour = Storage space (GB) × Unit price of storage (USD per GB)
Unit prices
Region | Unit price (USD per GB-hour) |
Regions other than SAU (Riyadh - Partner Region) | 0.000319 |
SAU (Riyadh - Partner Region) | 0.0003828 |
Outbound Internet traffic
You are charged only for outbound Internet traffic on an ApsaraMQ for RabbitMQ Serverless Edition instance.
If the Internet access feature is not enabled, you are not charged Internet traffic fees.
Billing formula
Internet traffic fees per hour = Total amount of outbound Internet traffic (GB) × Unit price of Internet traffic (USD per GB)
Unit prices
Region | Unit price (USD per GB) |
Regions other than SAU (Riyadh - Partner Region) | 0.13 |
SAU (Riyadh - Partner Region) | 0.156 |
Message traces
If you enable the message trace feature for an ApsaraMQ for RabbitMQ Serverless Edition instance, you are charged for the feature based on the number of logs that are generated for message traces.
Billing formula
Message trace fees per hour = Number of logs generated for message traces × Unit price of message traces (USD per message trace)
Rules for calculating API calls to different operations
If you call the following API operations during messaging, logs are generated for message traces, regardless of whether the API calls are successful. You are charged for the logs.
BasicAck
BasicConsume
BasicGet
BasicNAck
BasicReject
SendMessage
PushMessage
Unit prices
Region | Unit price (USD per million message traces) |
Regions other than SAU (Riyadh - Partner Region) | 0.0155 |
SAU (Riyadh - Partner Region) | 0.0186 |
References
For information about how to create ApsaraMQ for RabbitMQ Serverless Edition instances, see Manage instances.
If you no longer require an ApsaraMQ for RabbitMQ Serverless Edition instance, you can unsubscribe from the instance. For more information, see Unsubscribe from instances.
ApsaraMQ for RabbitMQ also supports the subscription billing method. For information about the billable items of subscription instances, see Billing of subscription instances.