Amazon MQ for RabbitMQ sizing guidelines - Amazon MQ
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon MQ for RabbitMQ sizing guidelines

You can choose the broker instance type that best supports your application. When choosing an instance type, it is important to consider factors that will affect broker performance:

  • the number of clients and queues

  • the volume of messages sent

  • messages kept in memory

  • redundant messages

Smaller broker instance types can be used for testing application performance. Larger broker instance types can handle production levels of clients and queues, high throughput, messages in memory, and redundant messages.

It is important to test your brokers to determine the appropriate instance type and size for your workload messaging requirements. Use the following sizing guidelines to determine the best appropriate instance type for your application:

Instance Type Deployment mode Maximum number of connections Maximum number of channels
t3.micro Single instance 500 1,500
m5.large Single instance 5,000 15,000
Cluster 15,000 45,000
m5.xlarge Single instance 10,000 30,000
Cluster 30,000 90,000
m5.2xlarge Single instance 20,000 60,000
Cluster 60,000 180,000
m5.4xlarge Single instance 40,000 120,000
Cluster 120,000 360,000

The following error messages are returned when connect or channel limits are exceeded.


ConnectionClosedByBroker 1500 "NOT_ALLOWED - number of channels opened on node '' has reached the maximum allowed limit of (1500)"


ConnectionClosedByBroker 500 "NOT_ALLOWED - connection refused: node connection limit (500) is reached"