AWS amazon-mq documentation change
Summary
Restructured sizing guidelines documentation by removing detailed tables and consolidating content. Added references to external resource limit pages, removed redundant sections about m5/m7g instance types, and simplified error message explanations.
Security assessment
The changes focus on documentation organization and instance type recommendations rather than addressing security vulnerabilities or describing security features. No security advisories, CVEs, or access control changes are mentioned. The modifications primarily improve clarity and navigation by linking to external resource limit pages.
Diff
diff --git a/amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md b/amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md index 843c78d7e..14c0d4193 100644 --- a//amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md +++ b//amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md @@ -5,2 +4,0 @@ -m7g single instance deployment sizing guidelinesm7g cluster deployment sizing guidelinesError messages - @@ -9 +7 @@ m7g single instance deployment sizing guidelinesm7g cluster deployment sizing gu -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: +You can choose the broker instance type that best supports your application. When choosing an instance type, consider factors that will affect broker performance: @@ -22,3 +20 @@ You can choose the broker instance type that best supports your application. Whe -Smaller broker instance types (`m7g.medium`) are recommended only for testing application performance. We recommend larger broker instance types (`m7g.large` and above) for 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. +Smaller broker instance types `m7g.medium` are recommended only for testing application performance. We recommend larger broker instance types `m7g.large` and above or production levels of clients and queues, high throughput, messages in memory, and redundant messages. @@ -28,18 +24 @@ It is important to test your brokers to determine the appropriate instance type -You cannot downgrade a broker from an `mq.m5` instance type to an `mq.t3.micro` instance type. - -###### Important - -You cannot downgrade a broker from an `mq.m7g` instance type to an `mq.t3.micro` instance type. - -###### Topics - - * m7g single instance deployment sizing guidelines - - * m7g cluster deployment sizing guidelines - - * Error messages - - - - -## Sizing guidelines for m7g with quorum queues for single instance deployment +You cannot downgrade a broker from an `mq.m5` or `mq.m7g` instance type to an `mq.t3.micro` instance type. @@ -47 +26 @@ You cannot downgrade a broker from an `mq.m7g` instance type to an `mq.t3.micro` -The following table shows the **maximum** limit values for each instance type for single instance brokers. +It is important to test your brokers to determine the appropriate instance type and size for your workload messaging requirements. @@ -49,10 +28 @@ The following table shows the **maximum** limit values for each instance type fo -Instance Type | Connections | Channels | Consumers per channel | Queues | Vhosts | Shovels ----|---|---|---|---|---|--- -mq.m7g.medium | 100 | 500 | 1,000 | 2,500 | 10 | 150 -mq.m7g.large | 5,000 | 15,000 | 1,000 | 20,000 | 1500 | 250 -mq.m7g.xlarge | 10,000 | 30,000 | 1,000 | 30,000 | 1,500 | 500 -mq.m7g.2xlarge | 20,000 | 60,000 | 1,000 | 40,000 | 1,500 | 1,000 -mq.m7g.4xlarge | 40,000 | 120,000 | 1,000 | 60,000 | 1,500 | 2,000 -mq.m7g.8xlarge | 80,000 | 240,000 | 1,000 | 80,000 | 1,500 | 4,000 -mq.m7g.12xlarge | 120,000 | 360,000 | 1,000 | 100,000 | 1,500 | 6,000 -mq.m7g.16xlarge | 160,000 | 480,000 | 1,000 | 120,000 | 1,500 | 8,000 +Always use the default resource limits on RabbitMQ 4 broker to determine the appropriate instance size for your application according to Amazon MQ best practices. These default resource limits are based on types `m7g` instance type and quorum queues. @@ -60 +30 @@ mq.m7g.16xlarge | 160,000 | 480,000 | 1,000 | 120,000 | 1,500 | 8,000 -## Sizing guidelines for m7g with quorum queues for cluster deployment + * [Default resource limits for m7g single-instance deployment](./rabbitmq-resource-limits-configuration.html#default-values-single-instance) @@ -62 +32 @@ mq.m7g.16xlarge | 160,000 | 480,000 | 1,000 | 120,000 | 1,500 | 8,000 -The following table shows the **maximum** limit values for each instance type for cluster brokers. + * [Default resource limits for m7g cluster deployment](./rabbitmq-resource-limits-configuration.html#default-values-cluster-brokers) @@ -64,10 +33,0 @@ The following table shows the **maximum** limit values for each instance type fo -Instance Type | Connections | Channels | Consumers per channel | Queues | Vhosts | Shovels ----|---|---|---|---|---|--- -mq.m7g.medium | 100 | 500 | 1,000 | 100 | 10 | 50 -mq.m7g.large | 5,000 | 15,000 | 1,000 | 10,000 | 1,500 | 150 -mq.m7g.xlarge | 10,000 | 30,000 | 1,000 | 15,000 | 1,500 | 300 -mq.m7g.2xlarge | 20,000 | 60,000 | 1,000 | 20,000 | 1,500 | 600 -mq.m7g.4xlarge | 40,000 | 120,000 | 1,000 | 30,000 | 1,500 | 1,200 -mq.m7g.8xlarge | 80,000 | 240,000 | 1,000 | 40,000 | 1,500 | 2,400 -mq.m7g.12xlarge | 120,000 | 360,000 | 1,000 | 50,000 | 1,500 | 3,600 -mq.m7g.16xlarge | 160,000 | 480,000 | 1,000 | 60,000 | 1,500 | 4,800 @@ -75 +34,0 @@ mq.m7g.16xlarge | 160,000 | 480,000 | 1,000 | 60,000 | 1,500 | 4,800 -The following table shows the **maximum** limit values for each instance type for single instance brokers. @@ -77,6 +35,0 @@ The following table shows the **maximum** limit values for each instance type fo -Instance Type | Connections | Channels | Consumers per channel | Queues | Vhosts | Shovels ----|---|---|---|---|---|--- -m5.large | 5,000 | 15,000 | 1,000 | 30,000 | 1500 | 250 -m5.xlarge | 10,000 | 30,000 | 1,000 | 60,000 | 1500 | 500 -m5.2xlarge | 20,000 | 60,000 | 1,000 | 120,000 | 1500 | 1,000 -m5.4xlarge | 40,000 | 120,000 | 1000 | 240,000 | 1,000 | 2,000 @@ -84 +37 @@ m5.4xlarge | 40,000 | 120,000 | 1000 | 240,000 | 1,000 | 2,000 -The following table shows the **maximum** limit values for each instance type for cluster brokers. +You can increase the value of any limit up to the maximum values as defined by instance type and deployment mode. However, we strongly recommend you test the broker performance with the increased values before using in production. @@ -86,6 +39 @@ The following table shows the **maximum** limit values for each instance type fo -Instance Type | Queues | Consumers per channel | Shovels ----|---|---|--- -m5.large | 10,000 | 1,000 | 150 -m5.xlarge | 15,000 | 1,000 | 300 -m5.2xlarge | 20,000 | 1,000 | 600 -m5.4xlarge | 30,000 | 1,000 | 1200 + * [Maximum resource limits for m7g single-instance deployment](./rabbitmq-resource-hard-limit.html#sizing-guidelines-m7g-single-instance) @@ -93 +41 @@ m5.4xlarge | 30,000 | 1,000 | 1200 -The following connection and channel limits are applied per node: + * [Maximum resource limits for m7g cluster deployment](./rabbitmq-resource-hard-limit.html#sizing-guidelines-m7g-cluster) @@ -95,6 +43 @@ The following connection and channel limits are applied per node: -Instance Type | Connections | Channels ----|---|--- -m5.large | 5000 | 15,000 -m5.xlarge | 10,000 | 30,000 -m5.2xlarge | 20,000 | 60,000 -m5.4xlarge | 40,000 | 120,000 + * [Maximum resource limits for m5 single-instance deployment](./rabbitmq-resource-hard-limit.html#sizing-guidelines-single-instance) @@ -102 +45 @@ m5.4xlarge | 40,000 | 120,000 -The exact limit values for a cluster broker may be lower than the indicated value depending on the number of available nodes and how RabbitMQ distributes resources among the available nodes. If you exceed the limit values, you can create a new connection to a different node and try again, or you can upgrade the instance size to increase the maximum limits + * [Maximum resource limits for m5 cluster deployment](./sizing-guidelines-cluster.html) @@ -104 +47 @@ The exact limit values for a cluster broker may be lower than the indicated valu -## Error messages + * [Error messages](./rabbitmq-resource-hard-limit.html#sizing-guidelines-limits-error-messages) @@ -106 +48,0 @@ The exact limit values for a cluster broker may be lower than the indicated valu -The following error messages are returned when limits are exceeded. All values are based on the `m7.large` single instance limits. @@ -108,13 +49,0 @@ The following error messages are returned when limits are exceeded. All values a -###### Note - -The error codes for the following messages may change based on the client library you are using. - -**Connection** - -`ConnectionClosedByBroker 500 "NOT_ALLOWED - connection refused: node connection limit (5000) is reached"` - -**Channel** - -`ConnectionClosedByBroker 1500 "NOT_ALLOWED - number of channels opened on node '[email protected]' has reached the maximum allowed limit of (15,000)"` - -**Consumer** @@ -122 +50,0 @@ The error codes for the following messages may change based on the client librar -`ConnectionClosedByBroker: (530, 'NOT_ALLOWED - reached maximum (1,000) of consumers per channel')` @@ -126,13 +54 @@ The error codes for the following messages may change based on the client librar -The following error messages use the HTTP Management API format. - -**Queue** - -`{"error":"bad_request","reason":"cannot declare queue 'my_queue': queue limit in cluster (10,000) is reached"}]` - -**Shovel** - -`{"error":"bad_request","reason":"Validation failed\n\ncomponent shovel is limited to 150 per node\n"}` - -**Vhost** - -`{"error":"bad_request","reason":"cannot create vhost 'my_vhost': vhost limit of 1500 is reached"}` +RabbitMQ 3.13 brokers do not come with default resource limits, but we recommend you use the suggested defaults. @@ -146 +62 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Broker defaults +Instance types @@ -148 +64 @@ Broker defaults -Plugins +Default resource limits