All Products
Search
Document Center

ApsaraMQ for RabbitMQ:Manage instances

Last Updated:Oct 13, 2025

An ApsaraMQ for RabbitMQ instance is an independent resource entity. It provides an isolated server or service environment that receives, stores, and forwards messages. An instance contains basic resource elements, such as vhosts, exchanges, and queues. This topic describes how to create an instance, view instance details, upgrade or downgrade the instance configuration, and renew the instance in the ApsaraMQ for RabbitMQ console.

Instance status

The status of an ApsaraMQ for RabbitMQ instance varies based on its billing method and edition.

Table 1. Instance status

Instance status

Description

Deploying

  • The instance is unavailable.

  • Platinum Edition instances require deployment by technical personnel after purchase. Therefore, only Platinum Edition instances enter the Deploying state.

In Service

  • The instance is available.

  • Professional Edition and Enterprise Edition instances enter the In Service state immediately after purchase.

Stopped

  • The instance is unavailable.

  • The instance resources and data are retained and can be recovered.

Released

  • The instance is unavailable.

  • The instance resources and data are deleted and cannot be recovered.

Supported operations

Operation

Description

Create an instance

ApsaraMQ for RabbitMQ provides various instance types. For more information about the differences between instance types, see Instance types.

Note

Serverless instances are currently available only in some regions. Support for other regions will be available soon. For information about the supported regions, see Supported regions. To enable Serverless instances in a specific region, submit a ticket to contact our helpdesk.

View instance details

In the ApsaraMQ for RabbitMQ console, view the basic information, endpoints, limits, messages, and peak transactions per second (TPS) of an instance.

Note

You can view the peak TPS of an instance only if the message trace feature is enabled for the instance.

Upgrade or downgrade instance configurations

  • When your business grows, you can increase the peak TPS or number of queues for your instance. This prevents business interruptions caused by resource constraints.

  • When your business slows, you can decrease the peak TPS or number of queues for your instance. This avoids resource waste and helps control costs.

You can upgrade or downgrade the following configuration items for subscription instances:

  • Instance type

  • Internet access

  • Internet TPS

  • Peak TPS

  • Number of queues

    Important

    For subscription Professional and Enterprise Edition instances, the cluster limits are related to the number of queues. If you change the number of queues for an instance, its cluster limits also change. For more information, see Cluster limits.

  • Message trace

  • Maximum connections (This applies to Enterprise and Platinum Edition instances.)

  • Message storage (This applies only to Platinum Edition instances.)

You can upgrade or downgrade the following configuration items for Serverless instances:

  • Internet access

  • Is message trace available?

  • Reserved capacity

Renew an instance

Renew your instance promptly to prevent service disruption caused by its release due to overdue payments.

Note
  • The instance must use the subscription billing method and be in the Expired or In Service state.

  • This operation applies only to the subscription billing method. For the pay-as-you-go billing method (no longer supported), just make sure your account balance is sufficient.

  • For more information about instance expiration, see Billing overview.

Enable the elastic TPS feature for an instance

Note

Only subscription instances support the elastic TPS feature.

If your business traffic has bursts that might exceed the peak TPS of your instance, enable the elastic TPS feature. This increases the upper limit of your instance's TPS within a certain range and prevents your instance from being throttled.

You are charged for the TPS that exceeds the base specification of your instance. For more information about the maximum elastic TPS limit and billing rules, see Elastic TPS billing.

Create an instance

  1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

  2. In the top menu bar, select a region. On the Instances page, click Create Instance.

  3. On the purchase page, set the basic configurations, select the service agreement, and then click Buy Now.

  4. Complete the payment as prompted.

    On the Instances page, select the region in the top menu bar to view the created instance.

    Note
    • Professional Edition and Enterprise Edition instances enter the Running state immediately after purchase.

    • Platinum Edition instances first enter the Deploying state after purchase. After a cluster is allocated, the instance enters the Running state.

View instance details

  1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

  2. In the top navigation bar of the Instances page, select the region where the instance that you want to manage resides. Then, in the instance list, click the name of the instance that you want to manage.

  3. On the Instance Details page, you can view the detailed information about the instance.

Upgrade or downgrade instance configurations

Usage notes

  • You can upgrade or downgrade the configuration only for instances that are in the In Service state.

  • When you upgrade a Professional or Enterprise Edition instance (shared cluster) to a Platinum Edition instance (exclusive cluster), the instance is migrated between clusters. The upgrade process takes about 30 to 60 minutes. The duration depends on the number of queues and the amount of data.

  • When you upgrade a Professional or Enterprise Edition instance to a Platinum Edition instance, the instance endpoint is not modified and client connections are not forcibly closed. However, the instance metadata is migrated. To shorten the backend upgrade time, upgrade the instance during off-peak hours.

  • If an upgrade or downgrade operation takes a long time and a message indicates that data is being migrated, it may be because data in a queue has not been fully consumed. To resolve this, check the queue and reduce the number of messages being produced or increase the number of consumers.

  • When you downgrade a Platinum Edition instance to a Professional or Enterprise Edition instance, instance data is not migrated, and your services are not affected.

  • Serverless instances can be converted between (Shared) Reserved + Elastic / Pay-by-usage and (Exclusive) Reserved + Elastic types.

    • When you upgrade a (Shared) Reserved + Elastic / Pay-by-usage instance to an (Exclusive) Reserved + Elastic instance, the instance data is migrated between clusters, and the domain name and IP mapping change. The server does not actively disconnect existing connections. Old connections remain on the pre-migration cluster until they are actively disconnected by the client.

    • When you convert an (Exclusive) Reserved + Elastic instance to a (Shared) Reserved + Elastic / Pay-by-usage instance, the instance data is migrated between clusters, and the domain name and IP mapping change. The server actively disconnects existing connections. The client needs to reconnect to the new cluster. The reconnection interval depends on the TCP disconnection time and DNS cache refresh time on the client side. Ensure that the client-side DNS cache is refreshed promptly and the application has a reconnection mechanism.

  • When you change the reserved TPS specification for a Serverless (Exclusive) Reserved + Elastic instance, the service nodes are scaled. For example, if you decrease the reserved TPS specification, the server reduces the number of service nodes. This may cause clients to experience a connection loss. Therefore, assess the potential impact on your services before you perform this operation.

Upgrade or downgrade operations

  1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

  2. In the top navigation bar of the Instances page, select the region where the instance that you want to manage resides. Then, in the instance list, click the name of the instance that you want to manage.

  3. On the Instance Details page, click Upgrade or Downgrade in the upper-right corner of the Overview section.

  4. In the Upgrade/Downgrade panel that appears, modify the instance specifications, select the service agreement, and then click Buy Now.

  5. Complete the payment as prompted.

Renew an instance

Important
  • Only subscription instances require renewal. Serverless instances do not require renewal.

  • The resources and data of an expired instance are retained and can be recovered by renewing the instance.

  • The resources and data of a released or deleted instance are not retained and cannot be recovered.

  1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

  2. In the top navigation bar of the Instances page, select the region where the instance that you want to manage resides. Then, in the instance list, click the name of the instance that you want to manage.

  3. On the Instance Details page, click Renew in the upper-right corner of the Overview section.

  4. In the Renew panel, select a subscription duration and the service agreement, and then click Buy Now.

  5. Complete the payment as prompted.

    Note

    To avoid service interruptions caused by overdue payments, enable auto-renewal.

    On the Instance Details page, in the Basic Information section, you can view the new Expired At of the instance.

Enable the elastic TPS feature for an instance

Note
  • If your Alibaba Cloud account has an overdue payment, you cannot enable the elastic TPS feature for an instance.

  • Only subscription instances support the elastic TPS feature.

  1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

  2. In the top navigation bar of the Instances page, select the region where the instance that you want to manage resides. Then, in the instance list, click the name of the instance that you want to manage.

  3. On the Instance Details page, in the Overview section, turn on the Enable Elastic Quota switch on the Maximum TPS card.

  4. In the dialog box that appears, carefully read the prompt and click OK.