All Products
Search

This Product

    ApsaraMQ for RabbitMQ:Manage instances

    Document Center

    ApsaraMQ for RabbitMQ:Manage instances

    Last Updated:Jun 02, 2026

    An ApsaraMQ for RabbitMQ instance is an independent resource entity that provides an isolated environment for receiving, storing, and forwarding messages. Each instance contains vhosts, exchanges, and queues. You can create instances, view instance details, upgrade or downgrade configurations, renew subscriptions, and enable elastic TPS in the console.

    Instance statuses

    Instance status depends on the billing method and edition.

    Status Available Description
    Deploying No The instance is being provisioned. Only Platinum Edition instances enter this state, as they require deployment by technical personnel after purchase.
    In Service Yes The instance is running. Professional and Enterprise Edition instances enter this state immediately after purchase.
    Stopped No The instance is unavailable. Resources and data are retained and can be recovered.
    Released No The instance is unavailable. Resources and data are permanently deleted and cannot be recovered.

    Prerequisites

    Complete the following steps before you manage an instance:

    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 your instance resides.

    Create an instance

    ApsaraMQ for RabbitMQ supports multiple instance types. For differences between them, see Instance types.

    Note

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

    1. On the Instances page, click Create Instance.

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

    3. Complete the payment as prompted.

    On the Instances page, select the target region to view the new 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

    View basic information, endpoints, limits, messages, and peak TPS of an instance.

    Note

    Peak TPS is visible only when the message trace feature is enabled.

    1. On the Instances page, click the name of the instance that you want to manage.

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

    Upgrade or downgrade instance configurations

    Adjust instance specifications to match workload changes. Upgrade to handle more traffic, or downgrade to reduce costs during off-peak periods.

    Configurable items

    The configurable items depend on the billing method of your instance.

    Subscription instances

    Configurable items for subscription instances:

    • Instance type

    • Internet access

    • Internet TPS

    • Peak TPS

    • Number of queues

      Important

      For subscription Professional and Enterprise Edition instances, cluster limits depend on the number of queues. Changing the queue count also changes the cluster limits. See Cluster limits.

    • Message trace

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

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

    Serverless instances

    Configurable items for Serverless instances:

    • Internet access

    • Message trace

    • Reserved capacity

    Usage notes

    Review the following before you upgrade or downgrade:

    General

    • Only instances in the In Service state can be upgraded or downgraded.

    Subscription edition changes

    • Professional/Enterprise to Platinum Edition upgrade: Migrates the instance from a shared cluster to an exclusive cluster. Takes 30–60 minutes depending on queue count and data volume. The endpoint remains unchanged and connections are not forcibly closed, but metadata is migrated. Perform this upgrade during off-peak hours.

    • Platinum to Professional/Enterprise Edition downgrade: Instance data is not migrated, and your services are not affected.

    • Long-running upgrades: If an upgrade or downgrade stalls with a data migration message, unconsumed messages in a queue may be the cause. Reduce message production or increase consumer count to resolve.

    Serverless type conversion

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

    • Shared to Exclusive: Data is migrated between clusters and the domain-to-IP mapping changes. The server does not disconnect existing connections. Old connections remain on the pre-migration cluster until the client disconnects.

    • Exclusive to Shared: Data is migrated between clusters and the domain-to-IP mapping changes. The server actively disconnects connections. Clients must reconnect to the new cluster. Reconnection timing depends on TCP teardown and DNS cache refresh on the client side. Ensure your application has a reconnection mechanism and refreshes DNS promptly.

    • Reserved TPS changes for Serverless (Exclusive): Changing the reserved TPS specification scales service nodes. Decreasing the reserved TPS may cause connection loss as nodes are removed. Assess the impact on your services before proceeding.

    Procedure

    1. On the Instances page, click the name of the instance that you want to manage.

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

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

    4. Complete the payment as prompted.

    Renew an instance

    Renew your subscription instance before it expires to prevent service disruption. For expiration and release policies, see Billing overview.

    Important

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

    • Resources and data of an expired instance are retained and can be recovered by renewal.

    • Resources and data of a released or deleted instance are permanently deleted and cannot be recovered.

    1. On the Instances page, click the name of the instance that you want to manage.

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

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

    4. Complete the payment as prompted.

    Note

    Enable auto-renewal to avoid service interruptions from overdue payments.

    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

    Enable elastic TPS to handle traffic bursts that exceed the peak TPS of your instance. This raises the TPS upper limit within a certain range and prevents throttling. You are charged for TPS that exceeds the base specification. For the maximum elastic TPS limit and billing rules, see Elastic TPS billing.

    Note

    • Only subscription instances support the elastic TPS feature.

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

    This feature appears as Enable Elastic Quota on the Maximum TPS card in the console.

    1. On the Instances page, click the name of the instance that you want to manage.

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

    3. In the confirmation dialog box, read the prompt and click OK.