All Products
Search
Document Center

ApsaraMQ for RabbitMQ:Billing overview

Last Updated:Jun 02, 2026

ApsaraMQ for RabbitMQ offers subscription and serverless (pay-as-you-go) billing. Choose a method based on your traffic volume and expected usage duration.

Instance types and billing methods

ApsaraMQ for RabbitMQ provides the following instance types and billing methods. For feature differences, see Instance types.

Billing method

Instance type

When to use

Fee estimation

Subscription

Professional Edition, Enterprise Edition, Enterprise Platinum Edition

Large, steady traffic that requires long-term capacity. Pay upfront to reserve resources at a discounted rate.

The buy page of subscription instances

Serverless (pay-as-you-go)

Pay-by-provisioned-capacity-and-elastic-traffic, Pay-by-messaging-request

Variable or unpredictable traffic. Pay only for actual usage with no upfront resource reservation.

Price calculator for serverless instances

Supported regions

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

Billable items

Billable items differ between subscription and serverless instances.

Subscription instances

The following diagram shows billable items for subscription instances. For details, see Billing of subscription instances.

image

Serverless instances

The following diagram shows billable items for serverless instances. Billing of serverless instances.

image

Instance expiration

Professional Edition, Enterprise Edition, and Enterprise Platinum Edition instances use subscription billing. The following diagram shows the instance lifecycle around expiration.

Instance expiration lifecycle

  • Before expiration

    The instance runs as expected.

  • Within 7 days after expiration

    The instance is frozen:

    • Messages cannot be sent or received.

    • The ApsaraMQ for RabbitMQ console cannot be used.

    • API operations cannot be called.

    Metadata for virtual hosts (vhosts), exchanges, and queues is temporarily retained.

    Renew the instance during this period to restore service. After renewal, normal operation resumes. For more information, see Renew an instance.

  • More than 7 days after expiration

    If you do not renew within 7 days after expiration, the instance is released. All metadata and message data are permanently deleted.

    To continue using ApsaraMQ for RabbitMQ, purchase a new instance. The new instance has a different ID and endpoint.