This topic describes the billing details for ApsaraMQ for MQTT Professional Edition instances.
Region restrictions
For a list of the regions that support Professional Edition instances, see Supported regions.
Billing components
The fees for a Professional Edition instance include two components: computing specifications (subscription) and Internet traffic (pay-as-you-go).
Computing specifications: These define the upper limits on the number of client connections, new connections per second, message read/write transactions per second (TPS), and the maximum number of subscription relationships for a single client. For more information about these specifications, see Capability limits of computing specifications.
Internet traffic: You are charged only for outbound Internet traffic. Inbound Internet traffic and traffic over a VPC are free of charge.
Computing specifications
Capabilities of computing specifications
Computing specifications define the upper limits for the following instance capabilities:
Maximum number of client connections: The maximum number of TCP connections from clients to an instance at any point in time. The number of connections is a transient value that is updated every minute.
Maximum number of new connections per second: The maximum number of new client connections that can be established for an instance per second.
Maximum message read/write TPS: The maximum total number of messages produced and consumed per second for an instance. Message read/write TPS is a transient value that is updated every minute.
Message TPS includes only messages that are sent and received using ApsaraMQ for MQTT. It does not include messages that are sent and received using ApsaraMQ for RocketMQ.
When message TPS is calculated, the value is multiplied by a specific factor based on the Quality of Service (QoS) level. For more information about the factors, see Billing factors.
For example, if a client is configured with QoS=2 and cleanSession=true, the billing factor is 5. If the client produces 10 messages, the number of produced messages is calculated as 10 × 5 = 50.
Maximum number of subscription relationships for a single client: The number of subscription relationships that are registered and retained for an instance. The number of subscription relationships is a transient value that is updated every minute.
The number of subscription relationships is calculated based on the subscriptions of each client (Client ID) to each ApsaraMQ for MQTT topic, regardless of the message sending scenario.
The subscriptions of the same client to a parent topic and its child topics are counted as separate subscription relationships.
For example, if Client_1 subscribes to TopicA, TopicA/sub_1, and TopicA/sub_2, the number of subscription relationships is 3.
If some of your clients are no longer in use and you do not need to retain their subscription relationships, purge the subscription relationships in a timely manner to conserve system resources. For more information, see Purge subscription relationships.
Billing rules
Item | Description |
Billable item | You are billed based on the computing specifications that you purchase. |
Billing method | Subscription You are billed based on the selected specifications and subscription duration. You must pay for resources before you use them. |
Billing cycle | Monthly |
Formula | Computing specification fee = Unit price (USD/month) × Subscription duration (months) |
Unit price | For more information about unit prices, see Unit prices. |
Capability limits of computing specifications
If the upper limits of your purchased instance type cannot meet your business requirements, we recommend that you upgrade the instance type in a timely manner. This prevents instance throttling, which occurs when the upper limits are exceeded and may cause client connection or message sending failures. To upgrade an instance, see Upgrade or downgrade an instance.
The following table describes the computing specifications for ApsaraMQ for MQTT Professional Edition instances and the capability limits of each specification.
Specification | Maximum number of client connections | Maximum number of new connections per second | Maximum total message read/write TPS (times/second) | Maximum number of subscription relationships | Maximum number of subscription relationships for a single client |
mqtt.p2.5xlarge | 5,000 | 100 | 5,000 | 150,000 | 30 |
mqtt.p2.10xlarge | 10,000 | 200 | 10,000 | 300,000 | |
mqtt.p2.50xlarge | 50,000 | 1,000 | 50,000 | 500,000 | |
mqtt.p2.100xlarge | 100,000 | 2,000 | 100,000 | 500,000 | |
mqtt.p2.200xlarge | 200,000 | 4,000 | 200,000 | 500,000 | |
mqtt.p2.500xlarge | 500,000 | 10,000 | 500,000 | 500,000 |
If the maximum specification (mqtt.p2.500xlarge) in the preceding table cannot meet your business requirements, submit a ticket to contact Alibaba Cloud technical support.
ApsaraMQ for MQTT no longer supports the 100 TPS specification. Existing instances with this specification can continue to be used, but they cannot be rolled back to this specification after an upgrade.
Unit prices
Region | Specification | Unit price (USD/month) |
China (Shanghai) | mqtt.p2.5xlarge | 168.42 |
mqtt.p2.10xlarge | 505.26 | |
mqtt.p2.50xlarge | 1178.95 | |
mqtt.p2.100xlarge | 2189.47 | |
mqtt.p2.200xlarge | 4421.05 | |
mqtt.p2.500xlarge | 11141.05 | |
Philippines (Manila), Indonesia (Jakarta), Malaysia (Kuala Lumpur) | mqtt.p2.5xlarge | 227.37 |
mqtt.p2.10xlarge | 682.11 | |
mqtt.p2.50xlarge | 1591.58 | |
mqtt.p2.100xlarge | 2955.79 | |
mqtt.p2.200xlarge | 5968.42 | |
mqtt.p2.500xlarge | 15040.42 | |
Hong Kong (China), Singapore, Japan (Tokyo), Germany (Frankfurt), US (Virginia), US (Silicon Valley), SAU (Riyadh - Partner Region) | mqtt.p2.5xlarge | 244.21 |
mqtt.p2.10xlarge | 732.63 | |
mqtt.p2.50xlarge | 1709.47 | |
mqtt.p2.100xlarge | 3174.74 | |
mqtt.p2.200xlarge | 6410.53 | |
mqtt.p2.500xlarge | 16154.53 |
Internet traffic
Billing rules
Item | Description |
Billable item | You are billed based on the total amount of outbound Internet traffic that you use and the usage duration. ApsaraMQ for MQTT bills you only for outbound Internet traffic. Inbound Internet traffic is free of charge. Outbound Internet traffic refers to the outbound Internet traffic that is generated when you use an Internet endpoint to connect to the ApsaraMQ for MQTT service. |
Billing method | Pay-as-you-go |
Billing cycle | You are billed on an hourly basis. |
Formula | Hourly Internet traffic fee = Total outbound Internet traffic in 1 hour × Unit price |
Unit prices for Internet traffic
Region | Unit price (USD/GB) |
All supported regions | 0.15 |
Billing example
Assume that you purchase a Professional Edition instance in the China (Hangzhou) region and use an Internet endpoint to connect to the instance. The outbound Internet traffic generated by the instance within one hour is as follows:
Time | 01 min | 02 min | 03 min | ... | 59 min | 60 points |
Generated outbound Internet traffic | 0.2 GB | 0.4 GB | 0 | No outbound traffic is generated | 1.5 GB | 0 |
The outbound Internet traffic fee for the instance in one hour is: (0.2 + 0.4 + 1.5) GB × USD 0.15/GB = USD 0.315.