AWS amazon-mq documentation change
Summary
Updated instance type references from t3/m5 to m7g series, added new m7g cluster deployment guidelines, adjusted connection/queue/shovel limits, and updated error message thresholds
Security assessment
Changes focus on updating hardware recommendations and performance limits rather than addressing security vulnerabilities. The modifications include instance type migrations (t3/m5 to m7g), adjusted scaling metrics, and error message value updates without any mention of security patches, vulnerabilities, or access controls.
Diff
diff --git a/amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md b/amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md index 3baca9626..65adfcad0 100644 --- a//amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md +++ b//amazon-mq/latest/developer-guide/rabbitmq-sizing-guidelines.md @@ -5 +5 @@ -Sizing guidelines for single instance deploymentSizing guidelines for cluster deploymentError messages +m7g single instance deployment sizing guidelinesm7g cluster deployment sizing guidelinesError messages @@ -22 +22 @@ You can choose the broker instance type that best supports your application. Whe -Smaller broker instance types (`t3.micro`) are recommended only for testing application performance. We recommend larger broker instance types (`m5.large` and above) for production levels of clients and queues, high throughput, messages in memory, and redundant messages. +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. @@ -26 +26,12 @@ It is important to test your brokers to determine the appropriate instance type -## Sizing guidelines for single instance deployment +###### 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 @@ -30,7 +41,27 @@ The following table shows the **maximum** limit values for each instance type fo -Instance Type | Connections | Channels | Queues | Consumers per channel | Shovels ----|---|---|---|---|--- -t3.micro | 500 | 1,500 | 2,500 | 1,000 | 150 -m5.large | 5,000 | 15,000 | 30,000 | 1,000 | 250 -m5.xlarge | 10,000 | 30,000 | 60,000 | 1,000 | 500 -m5.2xlarge | 20,000 | 60,000 | 120,000 | 1,000 | 1,000 -m5.4xlarge | 40,000 | 120,000 | 240,000 | 1,000 | 2,000 +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 + +## Sizing guidelines for m7g with quorum queues for cluster deployment + +The following table shows the **maximum** limit values for each instance type for cluster brokers. + +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 + +The following table shows the **maximum** limit values for each instance type for single instance brokers. @@ -38 +69,6 @@ m5.4xlarge | 40,000 | 120,000 | 240,000 | 1,000 | 2,000 -## Sizing guidelines for cluster deployment +Instance Type | Connections | Channels | Consumers per channel | Queues | Vhosts | Shovels +---|---|---|---|---|---|--- +m5.large | 5,000 | 15,000 | 30,000 | 1,000 | 1500 | 250 +m5.xlarge | 10,000 | 30,000 | 60,000 | 1,000 | 1500 | 500 +m5.2xlarge | 20,000 | 60,000 | 120,000 | 1,000 | 1500 | 1,000 +m5.4xlarge | 40,000 | 120,000 | 240,000 | 1500 | 1,000 | 2,000 @@ -62 +98 @@ 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 `m5.large` single instance limits. +The following error messages are returned when limits are exceeded. All values are based on the `m7.large` single instance limits. @@ -70 +106 @@ The error codes for the following messages may change based on the client librar -`ConnectionClosedByBroker 500 "NOT_ALLOWED - connection refused: node connection limit (500) is reached"` +`ConnectionClosedByBroker 500 "NOT_ALLOWED - connection refused: node connection limit (5000) is reached"` @@ -86 +122 @@ The following error messages use the HTTP Management API format. -`{"error":"bad_request","reason":"cannot declare queue 'my_queue': queue limit in cluster (30,000) is reached"}]` +`{"error":"bad_request","reason":"cannot declare queue 'my_queue': queue limit in cluster (10,000) is reached"}]` @@ -90 +126 @@ The following error messages use the HTTP Management API format. -`{"error":"bad_request","reason":"Validation failed\n\ncomponent shovel is limited to 250 per node\n"}` +`{"error":"bad_request","reason":"Validation failed\n\ncomponent shovel is limited to 150 per node\n"}` @@ -94 +130 @@ The following error messages use the HTTP Management API format. -`{"error":"bad_request","reason":"cannot create vhost 'my_vhost': vhost limit of 4,000 is reached"}` +`{"error":"bad_request","reason":"cannot create vhost 'my_vhost': vhost limit of 1500 is reached"}`