ApsaraMQ for RabbitMQ:Billing of serverless instances

Supported regions

Pay-as-you-go instances are available only in specific regions. For more information, see Supported regions.

Billable items

Serverless ApsaraMQ for RabbitMQ instances are billed on an hourly basis, regardless of whether the pay-by-provisioned-capacity-and-elastic-traffic or pay-by-messaging-request metering method is used. The following figure describes the billable items:

For information about the unit prices and billing formula of each billable item, see the following sections. You can also use the following price calculator to estimate your fees:

Rules for calculating numbers related to the messaging feature

The following rules can be used to calculate numbers in all billable items related to the messaging feature, including the number of messaging requests, provisioned capacity, and elastic traffic.

Number of messaging requests = Number of requests for receiving messages + Number of requests for delivering messages

• Number of requests for receiving messages: the number of requests initiated to receive messages in queues. For example, if a message that is received by an exchange is routed to three queues, three requests are counted to receive the message.

• Number of requests for delivering messages: the number of requests initiated to deliver messages. Each time a message is delivered, a request 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 requests 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 requests 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.

Messaging requests

If you use the pay-by-messaging-request metering method for a serverless ApsaraMQ for RabbitMQ instance, you are charged messaging fees based on the total number of messaging requests.

Billing formula

Messaging fees per hour = Total number of messaging requests × Unit price of messaging requests (USD per request)

Unit prices

Billing example

The following items describe the number of requests initiated to receive and deliver messages in an instance that resides in the China (Hangzhou) region in a specific hour:

• Seven million requests are initiated to receive normal messages and 2 million requests are initiated to receive delayed messages on the broker. The size of each message is 8 KB.

• Eight million requests are initiated to deliver normal messages and 3.2 million requests 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.

Provisioned capacity

If you use the pay-by-provisioned-capacity-and-elastic-traffic metering method for a serverless ApsaraMQ for RabbitMQ instance, messaging fees include fees for provisioned capacity and elastic traffic. You are charged the provisioned capacity fees based on the provisioned capacity and usage duration.

Billing formula

Provisioned capacity fee per hour = Provisioned capacity × Unit price of provisioned capacity (USD per TPS-hour)

Unit prices

Billing example

You purchase a serverless ApsaraMQ for RabbitMQ instance that uses the pay-by-provisioned-capacity-and-elastic-traffic metering method and has a provisioned capacity of 3,000 TPS in the China (Hangzhou) region. The provisioned capacity fee per hour is USD 0.39. The fee is calculated by using the following formula: 3,000 × 0.00013 = 0.39. The provisioned capacity fee per month (30 days) is USD 280.8. The fee is calculated by using the following formula: 0.39 × 24 × 30 = 280.8.

Elastic traffic

If you use the pay-by-provisioned-capacity-and-elastic-traffic metering method for a serverless ApsaraMQ for RabbitMQ instance, you are charged elastic traffic fees for the traffic that exceeds the provisioned capacity.

Billing formula

$$Elastictrafficfeeperhour=\sum _{1\le i\le 60}[Ti\times Amountofelastictraffic(TPS)]\times Unitpriceofelastictraffic(USDperTPS-minute)$$

In the preceding formula, Ti indicates the ith minute of the hour. For example, T1 indicates the first minute of the hour and T60 indicates the 60th minute of the hour. $$\sum$$indicates the total amount of elastic traffic used during the hour.

Unit prices

Billing example

You purchase a serverless ApsaraMQ for RabbitMQ instance that uses the pay-by-provisioned-capacity-and-elastic-traffic metering method and has a provisioned capacity of 5,000 TPS in the China (Hangzhou) region. The following table describes the traffic usage of the instance per minute within a specific hour.

The elastic traffic fee of the instance in this hour is USD 0.0114. The fee is calculated by using the following formula: (1 × 200 + 1 × 300 + 1 × 100) × 0.000019 = 0.0114.

Queues

You are charged queue fees for queues on a serverless ApsaraMQ for RabbitMQ 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 queues created 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 example

The following table describes the number of queues created on an instance in 2 hours on a specific day.

Message storage space

You are charged storage fees for a serverless ApsaraMQ for RabbitMQ 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

Outbound Internet traffic

You are charged only for outbound Internet traffic in a serverless ApsaraMQ for RabbitMQ instance.

If the Internet access feature is disabled, 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

Message traces

After you enable the message trace feature for a serverless ApsaraMQ for RabbitMQ instance, you are charged for the feature based on the number of logs that are generated for message traces.

If the message trace feature is disabled, no fees are generated.

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

References

• For information about how to create serverless ApsaraMQ for RabbitMQ instances, see Manage instances.

• If you no longer require a serverless ApsaraMQ for RabbitMQ 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.