ApsaraMQ for RabbitMQ Professional, Enterprise, and Platinum Edition instances are billed using the subscription method. This topic describes the billable items and billing rules for these instances.
Billable items
The fees for Professional, Enterprise, and Platinum Edition instances include the following items:
Instance specification billing (Required): Billed on a subscription basis.
Elastic TPS billing (Optional): Billed on a pay-as-you-go basis. Elastic TPS fees are charged only if you enable the elastic TPS feature for your instance.
TPS counting rules
The following API operations are billable. For more information about these operations, see Request methods.
ConnectionOpen and ChannelOpen
QueueDeclare, QueueDelete, QueueBind, and QueueUnbind
ExchangeDeclare and ExchangeDelete
ExchangeBind and ExchangeUnBind
SendMessage, BasicConsume, BasicGet, BasicAck, BasicReject, BasicNack, and BasicRecover
The number of API calls is calculated based on the following rules:
Delayed messages are a premium feature of ApsaraMQ for RabbitMQ. Sending a delayed message counts as five API calls. Consuming a delayed message counts as one API call.
Example: If you send two delayed messages and consume three delayed messages in one second, the total TPS is 13. Formula: 2 × 5 + 3 = 13 TPS.
When counting calls to the SendMessage operation, the number of calls is determined by the number of queues where the message is stored after routing.
For example, if you send one message to a Fanout exchange and it is routed to 10 queues, the SendMessage operation is counted as 10 calls.
If a message body is 64 KB or smaller, it is counted as one request. If the message body is larger than 64 KB, each 4 KB of data over the 64 KB limit is counted as an additional request.
Instance specification billing
Billing rules
Billable item | Required | Applicable instance editions | Free quota | Billing cycle |
Peak TPS | Yes. You are charged only when specific API operations are called. For more information, see TPS counting rules. |
| None | Month |
Internet traffic | No. You are charged for Internet traffic only if you enable Internet access. |
| None | |
Number of queues | Yes |
| Enterprise and Platinum Edition instances include a free quota. For the specific quota, see the instance specifications on the buy page. | |
Maximum connections | Yes |
| Enterprise and Platinum Edition instances include a free quota. For the specific quota, see the instance specifications on the buy page. | |
Message trace retention period | No. You are charged for message trace retention only if you enable the message trace feature. |
| Platinum Edition instances provide a 15-day message trace retention period for free. | |
Message storage space | Yes | Platinum Edition | None |
Pricing details
For more information about the pricing of instance specifications, see the ApsaraMQ for RabbitMQ buy page.
Elastic TPS billing
Description of billable items
Each ApsaraMQ for RabbitMQ instance has a peak TPS limit based on its specification. If your usage exceeds this limit, the instance is throttled. To prevent throttling due to burst traffic, you can enable the elastic TPS feature. For more information, see Enable the elastic TPS feature for an instance.
After you enable the elastic TPS feature, the peak TPS limit of the instance can increase within a specific range. You are charged for any TPS that exceeds the base specification limit.
The maximum elastic TPS for each instance edition is fixed and cannot be changed. For more information, see Unit prices.
Billing rules
Item | Description |
Billable item | You are charged for the TPS that exceeds the base peak TPS specification of the instance. Incremental TPS = Maximum runtime TPS - Base peak TPS specification For example, an instance has a base peak TPS specification of 5,000 TPS. If the runtime TPS of the instance reaches 6,200 TPS, you are charged an elastic TPS fee for the excess 1,200 TPS. |
Billing method | Pay-as-you-go (post-paid). Fees are automatically deducted from your Alibaba Cloud account. |
Billing cycle | Per minute |
Billing formula | Elastic TPS fee per minute = Incremental TPS per minute × Unit price of elastic TPS |
Unit prices
Instance edition | Professional Edition | Enterprise Edition | Platinum Edition | |
Maximum elastic TPS | 0.5 times the base specification | 1 time the base specification, up to 50,000 TPS | 1 time the base specification, up to 50,000 TPS | |
Unit price of elastic TPS (USD/TPS/minute) | Other regions | 0.000072 | 0.000072 | 0.000288 |
UAE (Dubai) region | 0.000144 | 0.000144 | 0.000576 | |
SAU (Riyadh - Partner Region) region | 0.000086 | 0.000086 | 0.000346 | |
"Other regions" in the preceding tables refers to all regions where ApsaraMQ for RabbitMQ is available, except for the SAU (Riyadh - Partner Region) region. For a list of supported regions, see Supported regions.
The maximum elastic TPS for Enterprise and Platinum Edition instances is 50,000. For example, if an Enterprise Edition instance has a base peak TPS of 80,000, its maximum elastic TPS is still 50,000. Therefore, the total peak TPS for the instance is 130,000.
Billing example
Assume that you have a Professional Edition instance in the China (Hangzhou) region with a base specification of 1,000 TPS. The following table shows the instance's runtime status over one hour:
Time | 00 min | 01 min | 02 min | 03 min | ... | 58 min | 59 min |
Actual peak TPS (TPS) | 1200 | 1300 | 800 | 850 | All < 1,000 | 950 | 1100 |
Incremental TPS (TPS) | 200 | 300 | 0 | 0 | 0 | 0 | 100 |
The elastic TPS fee for this hour is USD 0.0432. Formula: (200 + 300 + 100) × 0.000072 = 0.0432.