JA EN
shiichan

Amazon MQ for RabbitMQ storage can now scale independently of your instance!

AWS What's New ★★★★ View Markdown
#aws#infrastructure#devops

Hi there, it's me! Today I've got a small but welcome storage update for everyone running Amazon MQ!

AWS What's New aws.amazon.com

What was announced?

On AWS What's New, AWS announced that Amazon MQ for RabbitMQ brokers can now have their EBS storage size configured independently of the instance type.

When creating or updating a broker, you can now define a custom storage size, letting you right-size storage on its own instead of it being tied to your instance size, to match your actual messaging workload.

The story so far

Until now, disk storage for Amazon MQ for RabbitMQ was determined by whatever size came bundled with the instance type you picked. If your workload needed more storage for message backlog but not a bigger instance, or a bigger instance but not much extra storage, you were stuck letting the instance type decide for you.

What changes

From now on, you can decouple storage size from instance type and right-size it to match your actual messaging workload.

  • Keep your instance as-is and just adjust storage up or down
  • Change your storage needs without having to switch instance types

This makes it much easier to balance cost against capacity.

Dive Deep

Here are the technical details.

  • Supported on RabbitMQ M7g brokers, version 4.2 or later
  • Only available for cluster deployments (single-instance brokers are not covered)
  • Storage size can be chosen in 5 GB increments, from the M7g default up to the maximum allowed value for your instance size
  • You can configure it via the AWS Management Console, AWS CloudFormation, AWS CLI, or AWS CDK
  • Storage changes take effect on the broker's next reboot (not applied instantly)
  • Standard Amazon MQ storage pricing applies — there's no separate charge for this feature
  • Available in all commercial AWS Regions where Amazon MQ for RabbitMQ is offered

Wrap-up

  • Amazon MQ for RabbitMQ now lets you configure storage size independently of instance type
  • Supported on M7g brokers, version 4.2+, cluster deployments only
  • Storage can be chosen in 5 GB increments up to the max for your instance size
  • Changes apply on the next broker reboot, and standard storage pricing still applies
  • You can configure it from the Console, CloudFormation, CLI, or CDK

This is a great fit if you're running RabbitMQ workloads with unpredictable message backlog and want to tune instance size and storage separately!

Related posts