ApsaraMQ for RabbitMQ:Billing of serverless instances

Supported regions

Serverless instances are available only in specific regions. For more information, see Supported regions.

Billable items at a glance

The following table lists all billable items. For unit prices and formulas, see the corresponding sections.

How messages are counted

These counting rules apply to all message-related billable items: messages sent and received, reserved capacity, and elastic traffic.

Total messages = Messages received by queues + Messages delivered to consumers

• Messages received: Counted per queue. If an exchange routes one message to three queues, that counts as three received messages.

• Messages delivered: Each successful delivery counts as one, regardless of whether the consumer returns an ACK.

• Payload size: A message of 4 KB or smaller counts as one message. For larger messages, divide the size by 4 KB and round up. For example, an 18 KB message counts as ⌈18/4⌉ = 5 messages.

  Note

  ⌈ ⌉ denotes the ceiling function (round up to the nearest integer).

Messages sent and received

*Applies to: Pay-by-Cumulative-Usage billing type only*

Normal messages (received + delivered): (7 + 8) × 2 × 0.31 = USD 9.30
Delayed messages received:              2 × 2 × 1.55       = USD 6.20
Delayed messages delivered:             3.2 × 2 × 0.31     = USD 1.984

Total hourly fee:                                           = USD 17.484

Reserved capacity

*Applies to: Reserved + Elastic billing type only*

The reserved capacity fee is a fixed hourly charge based on the TPS capacity you select when purchasing the instance.

Hourly fee:  3,000 × 0.00013 = USD 0.39
Monthly fee: 0.39 × 24 × 30  = USD 280.8  (assuming 30 days)

Elastic traffic

*Applies to: Reserved + Elastic billing type only*

When the actual TPS exceeds the reserved capacity during any minute within the hour, the excess is billed as elastic traffic. The system samples the peak TPS for each of the 60 minutes and sums the overage.

Queues

Queue fees are based on the peak number of queues that exist in the instance during each hour.

Message storage

The storage fee covers the total storage space occupied by all messages in the instance, including consumed messages. The maximum message retention period is 3 days.

Outbound Internet traffic

This fee applies only when public network access is enabled.

Message trace

This fee applies only when message trace is enabled. The system generates trace logs for specific API operations, and all generated logs are billed regardless of whether the message is sent or received successfully.

The following API operations generate trace logs:

• BasicAck

• BasicConsume

• BasicGet

• BasicNAck

• BasicReject

• SendMessage

• PushMessage

Instance fee

PrivateLink

If you enable a PrivateLink endpoint, additional fees apply when you access ApsaraMQ for RabbitMQ through it. For pricing details, see PrivateLink endpoints.

FAQ

Q: How do I choose between Reserved + Elastic and Pay-by-Cumulative-Usage?

Choose Reserved + Elastic if your messaging workload has a predictable baseline throughput. Reserving capacity upfront costs less per TPS than elastic overage pricing. Choose Pay-by-Cumulative-Usage if your traffic is highly variable or you want to avoid committing to a fixed capacity.

Q: How are messages counted when one message is routed to multiple queues?

Each queue that receives the message counts as one received message. If an exchange routes a single message to three queues, that counts as three received messages.

Q: What happens if my traffic exceeds the reserved capacity?

Traffic above the reserved capacity is automatically billed as elastic traffic on a per-minute basis. The excess is billed at the elastic traffic rate.

Q: Are deleted queues still billed?

Queue fees are based on the peak queue count during each billing hour. If you create 300 queues and delete 100 within the same hour, you are billed for 300 queues for that hour.

What's next

• Create a Serverless instance

• Release an instance (refund policy)

• ApsaraMQ for RabbitMQ also supports subscription instances. For more information about the billable items, see Billing of subscription instances.