An ApsaraMQ for RabbitMQ instance is an independent resource entity that provides an isolated environment for receiving, storing, and forwarding messages. Each instance contains core resource elements such as vhosts, exchanges, and queues. This topic describes how to create an instance, view instance details, upgrade or downgrade configurations, renew a subscription, and enable elastic TPS in the ApsaraMQ for RabbitMQ console.
Instance statuses
The status of an ApsaraMQ for RabbitMQ instance depends on its billing method and edition.
| Status | Available | Description |
|---|---|---|
| Deploying | No | The instance is being provisioned. Only Platinum Edition instances enter this state because they require deployment by technical personnel after purchase. |
| In Service | Yes | The instance is operational and ready for use. Professional Edition and Enterprise Edition instances enter this state immediately after purchase. |
| Stopped | No | The instance is unavailable. Instance resources and data are retained and can be recovered. |
| Released | No | The instance is unavailable. Instance resources and data are permanently deleted and cannot be recovered. |
Prerequisites
Before you perform any instance management operation, complete the following steps:
Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.
In the top navigation bar of the Instances page, select the region where your instance resides.
Create an instance
ApsaraMQ for RabbitMQ provides various instance types. For more information about the differences between instance types, see Instance types.
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.
On the Instances page, click Create Instance.
On the purchase page, set the basic configurations, select the service agreement, and then click Buy Now.
Complete the payment as prompted.
On the Instances page, select the region in the top menu bar to view the created instance.
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
You can view the basic information, endpoints, limits, messages, and peak transactions per second (TPS) of an instance in the console.
You can view the peak TPS of an instance only if the message trace feature is enabled for the instance.
On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, you can view the detailed information about the instance.
Upgrade or downgrade instance configurations
When your workload changes, you can adjust instance specifications to match demand. Upgrade to handle increased traffic or add capacity, or downgrade to reduce costs during quieter periods.
Configurable items
The configurable items depend on the billing method of your instance.
Subscription instances
You can upgrade or downgrade the following configuration items for subscription instances:
Instance type
Internet access
Internet TPS
Peak TPS
Number of queues
ImportantFor 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.)
Serverless instances
You can upgrade or downgrade the following configuration items for Serverless instances:
Internet access
Is message trace available?
Reserved capacity
Usage notes
Before you upgrade or downgrade an instance, review the following considerations:
General
You can upgrade or downgrade the configuration only for instances that are in the In Service state.
Subscription edition changes
Professional/Enterprise to Platinum Edition upgrade: This upgrade migrates the instance from a shared cluster to an exclusive cluster. The process takes approximately 30 to 60 minutes, depending on the number of queues and the amount of data. The instance endpoint is not modified and client connections are not forcibly closed. However, instance metadata is migrated. To minimize the impact on your workload, perform the 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 takes a long time and a message indicates that data is being migrated, this may be because data in a queue has not been fully consumed. To resolve this issue, check the queue and reduce the number of messages being produced or increase the number of consumers.
Serverless type conversion
Serverless instances can be converted between (Shared) Reserved + Elastic / Pay-by-usage and (Exclusive) Reserved + Elastic types.
Shared to Exclusive: 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.
Exclusive to Shared: 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.
Reserved TPS changes for Serverless (Exclusive): 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. Assess the potential impact on your services before you perform this operation.
Procedure
On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, click Upgrade or Downgrade in the upper-right corner of the Overview section.
In the Upgrade/Downgrade panel that appears, modify the instance specifications, select the service agreement, and then click Buy Now.
Complete the payment as prompted.
Renew an instance
Renew your subscription instance before it expires to prevent service disruption caused by its release due to overdue payments. For more information about instance expiration, see Billing overview.
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.
On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, click Renew in the upper-right corner of the Overview section.
In the Renew panel, select a subscription duration and the service agreement, and then click Buy Now.
Complete the payment as prompted.
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
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.
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.
In the console, this feature is labeled Enable Elastic Quota on the Maximum TPS card.
On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, in the Overview section, turn on the Enable Elastic Quota switch on the Maximum TPS card.
In the dialog box that appears, carefully read the prompt and click OK.