This topic describes the billing methods and billable items of Simple Message Queue (formerly MNS), and the pricing details for Simple Message Queue (formerly MNS).
Billing method
Simple Message Queue (formerly MNS) supports only the pay-as-you-go billing method. Fees are settled hourly and a bill is generated every 24 hours. Each day, Alibaba Cloud measures your service usage from the previous day, generates a bill, and automatically deducts the fees from your Alibaba Cloud account.
You can use the Simple Message Queue (formerly MNS) pricing calculator to estimate your costs:
Billable items
The following diagram shows the billable items for Simple Message Queue (formerly MNS).
Queue resource usage fees
Fees are charged daily based on the number of queues used.
Billing formula
Queue resource usage fees = Number of queues × Unit price of a queue (USD/queue/day)
Unit price
Region | Unit price (USD/queue/day) |
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Ulanqab) | 0.08 |
China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Thailand (Bangkok), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), US (Atlanta), UAE (Dubai), Malaysia (Kuala Lumpur), Indonesia (Jakarta) | 0.11 |
SAU (Riyadh - Partner Region) | 0.132 |
Each queue is billed once per day. The fees are charged to the Alibaba Cloud account that owns the queue.
Delete queues that are no longer in use to avoid unnecessary fees.
Billing example
For example, you create queues in the China (Hangzhou) region. The number of queues created and the fees are as follows:
Time | Number of queues created | Number of billable queues | Unit price | Total fees |
Day 1 |
| 30 | Unit price: 0.08 (USD/queue/day) | 0.08 × 30 = 2.4 USD |
Day 2 | 50 more have been created. | 50 + 20 = 70 | Unit price: 0.08 (USD/queue/day) | 0.08 × 70 = 5.6 USD |
Queue request fees
Counting rules
The size of a request is measured in 64 KB increments. For example, a 256 KB message request is counted as four requests for billing (256/64 = 4).
All requests sent to a queue are counted.
After you delete a queue, stop sending requests to it. You are still charged for requests that are sent using an SDK.
Billing formula
Queue request fees = Total number of queue requests (in millions) × Unit price per million queue requests (USD/million requests)
Unit price
Each Alibaba Cloud account receives a free quota of 20 million requests per month for Simple Message Queue (formerly MNS). You are charged for requests that exceed this quota.
The free quota applies only to normal messages. Ordered messages are not covered by the free quota and are charged based on the standard billing rules.
The following tables list the unit prices for queue requests.
Region | Unit price (USD/million requests) | |
Normal messages | Ordered messages | |
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Ulanqab) | 0.32 | 0.48 |
Malaysia (Kuala Lumpur), Indonesia (Jakarta) | 0.43 | 0.645 |
China (Hong Kong), Singapore, Japan (Tokyo), US (Virginia), US (Silicon Valley), US (Atlanta), Germany (Frankfurt), UAE (Dubai), UK (London), Thailand (Bangkok), South Korea (Seoul) | 0.46 | 0.69 |
SAU (Riyadh - Partner Region) | 0.552 | 0.828 |
Billing example
For example, you create a Simple Message Queue (formerly MNS) standard queue in the China (Hangzhou) region. The unit price for queue requests is USD 0.32 per million requests. After you use the monthly free quota of 20 million requests, you are charged for any additional requests. For example, if you make 22 million queue requests, you are charged for the 2 million requests that exceed the free quota. Your queue request fees are 2 × 0.32 = 0.64 USD.
Topic resource usage fees
Fees are charged daily based on the number of topics used.
Billing formula
Topic resource usage fees = Number of topics × Unit price of a topic (USD/topic/day)
Unit price
Region | Unit price (USD/topic/day) |
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Ulanqab) | 0.32 |
Malaysia (Kuala Lumpur), Indonesia (Jakarta) | 0.43 |
China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Thailand (Bangkok), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), US (Atlanta), UAE (Dubai) | 0.46 |
SAU (Riyadh - Partner Region) | 0.552 |
Each topic is billed once per day. The fees are charged to the Alibaba Cloud account that owns the topic.
Delete topics that are no longer in use to avoid unnecessary fees.
Billing example
For example, you create topics in the China (Hangzhou) region. The number of topics created and the fees are as follows:
Time | Number of topics created | Number of billable topics | Unit price | Total fees |
Day 1 |
| 30 | Unit price: 0.32 (USD/topic/day) | 0.32 × 30 = 9.6 USD |
Day 2 | 50 more topics are created. | 50 + 20 = 70 | Unit price: 0.32 (USD/topic/day) | 0.32 × 70 = 22.4 USD |
Topic request fees
Counting rules
The size of a request is measured in 64 KB increments. For example, a 256 KB message request is counted as four requests for billing (256/64 = 4).
All requests sent to a topic are counted.
After you delete a topic, stop sending requests to it. You are still charged for requests that are sent using an SDK.
Billing formula
Topic request fees = Total number of topic requests (in millions) × Unit price per million topic requests (USD/million requests)
Unit price
Each Alibaba Cloud account receives a free quota of 20 million requests per month for Simple Message Queue (formerly MNS). You are charged for requests that exceed this quota.
The free quota applies only to normal messages. Ordered messages are not covered by the free quota and are charged based on the standard billing rules.
The following tables list the unit prices for topic requests.
Region | Unit price (USD/million requests) | |
Normal messages | Ordered messages | |
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Ulanqab) | 0.32 | 0.48 |
Malaysia (Kuala Lumpur), Indonesia (Jakarta) | 0.43 | 0.645 |
China (Hong Kong), Singapore, Japan (Tokyo), US (Virginia), US (Silicon Valley), US (Atlanta), Germany (Frankfurt), UAE (Dubai), UK (London), Thailand (Bangkok), South Korea (Seoul) | 0.46 | 0.69 |
SAU (Riyadh - Partner Region) | 0.552 | 0.828 |
Billing example
For example, you create a Simple Message Queue (formerly MNS) standard topic in the China (Hangzhou) region. The unit price for topic requests is USD 0.32 per million requests. After you use the monthly free quota of 20 million requests, you are charged for any additional requests. For example, if you make 22 million topic requests, you are charged for the 2 million requests that exceed the free quota. Your topic request fees are 2 × 0.32 = 0.64 USD.
Subscription push fees
Push fees for HTTP subscriptions are temporarily free of charge. You will be notified of the official billing start date through announcements, text messages, and internal messages.
Subscription type | Billing |
Queue | Pushing messages to queues is free of charge. For more information about queue usage fees, see Queue resource usage fees and Queue request fees. |
HTTP | For messages pushed to an HTTP service, you are charged based on the total number of pushes. |
Outbound Internet traffic fees
Outbound Internet traffic generated by Simple Message Queue (formerly MNS) is temporarily free of charge. You will be notified of the official billing start date through announcements, text messages, and internal messages.
Message trace fees
If you enable the message trace feature, Simple Message Queue (formerly MNS) charges you based on the number of message traces.
Message trace counting rules
The number of message traces is calculated based on the number of messages sent by producers and delivered to consumers. The formula is as follows: Number of messages received by the server from producers + (Number of messages delivered by the server to consumers × 2).
During message consumption, a message trace is recorded in two stages: before the message enters the consumption logic and after the consumption logic is complete. Therefore, each message delivered to a consumer is counted as two traces.
Billing formula
Hourly message trace fees = Number of message traces × Unit price per trace (USD/trace)
Unit price
Region | Message trace unit price (USD/million traces) |
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Guangzhou), China (Chengdu), China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), US (Atlanta), Mexico, UAE (Dubai), SAU (Riyadh - Partner Region), Thailand (Bangkok) | 0.0155 |
Billing example
For example, if your application in the China (Beijing) region sends 1 million messages per day and each message is consumed once, the number of message traces generated per day is calculated as follows:
Message sending: 1 million traces
Message consumption: 2 million traces
Total per day: 3 million traces
Daily fees: 3 million traces × USD 0.0155 per million traces = 0.0465 USD