Docs

Message Queue for RabbitMQ

Instance management

Change instance specifications

After creating an instance, if your business scale grows and the current instance specifications no longer meet your needs, you can increase its computing and storage specifications accordingly to avoid reduced processing capacity caused by resource limits or abnormal business operations. If the business scale shrinks, you can lower the instance's computing specifications to prevent wasted resources and reduce costs. This topic describes how to change instance specifications in the Message Queue for RabbitMQ Console.

Prerequisites

A RabbitMQ instance has been created, and the instance status is Running.

Note

If you need to change instance specifications, note the following restrictions and potential risks.

Category	Description
Limits	Cluster instances do not support the conversion to standalone instances. Currently, you can upgrade computing specifications and expand storage, or downgrade computing specifications. Storage cannot be reduced. Different computing specifications correspond to different storage capacity ranges. When upgrading the instance's computing specification, the storage capacity must be upgraded synchronously. Pricing varies based on computing specifications and storage capacity. After changing the instance specification, configuration fees will change. Confirm the related fees in the order. When downgrading specifications, you can only switch to a smaller specification with the same number of nodes. Switching to a specification with a different number of nodes is not supported. For example, rabbitmq.n3.x2.medium can be downgraded to rabbitmq.n3.x2.small. "n3" means the number of nodes is 3. Similarly, rabbitmq.n3.x2.medium cannot be downgraded to rabbitmq.n1.x2.medium. When changing the specification, upgrading or downgrading between x4 and x2 specifications is not supported. For example, rabbitmq.n3.x4.medium cannot be changed to rabbitmq.n3.x2.medium.
Risks	Do not perform other operations on the instance during the specification change process. Otherwise, abnormal instance status or other issues may appear. During configuration changes, server nodes restart sequentially. It is recommended to perform this operation during off-peak business hours. The client may briefly disconnect and then reconnect with some nodes. Errors may occur. Messages that have already been sent successfully will not be lost after the configuration change. For messages that fail to send during the configuration change, retry is recommended. You can configure a retry mechanism on the client. When using mirror queues, always ensure that data replicas are synchronized in real time. Mirror queues have potential usage risks. During specification changes and restarts, synchronization may fail. In this case, manual intervention is required to restore synchronization. When an instance starts, it loads the queue's historical data index. If there are too many historical queues, memory usage may increase. It is recommend to clear unused queues promptly. You can also configure queue TTL to automatically recycle inactive queues. For detailed steps, see Configuring queue TTL.

Operation steps

Select a region on the top menu bar.

Find the specified instance on the Instances page, then click Change Configuration in the Actions column.

On the Change configuration page, select the new instance compute configuration and storage specifications.

Click Confirm order.

Confirm the modified specifications, read and agree to the relevant agreements, and click Buy now.

Confirm the order details and follow the page prompts to make payment.

tip

The configuration change is expected to take about 30 minutes. The overall service will not be affected, though there may be rare cases of unordered consumption.

Execution result

On the Instances page, click the instance name of the modified instance.

On the Basic information tab, you can view the updated configuration of the instance.

You can view details of specification change tasks on the Task management tab.

Last updated: 2026.08.28 16:42:44