AWS amazon-mq documentation change
Summary
Updated connection limit troubleshooting to include RabbitMQ-specific guidance alongside ActiveMQ
Security assessment
The change expands general troubleshooting guidance for connection limits across both ActiveMQ and RabbitMQ brokers. No security vulnerabilities, exploits, or weaknesses are mentioned. The added RabbitMQ monitoring guidance (CloudWatch metrics/web console) is operational in nature.
Diff
diff --git a/amazon-mq/latest/developer-guide/troubleshooting-activemq.md b/amazon-mq/latest/developer-guide/troubleshooting-activemq.md index 1cf824785..6c23d7f6e 100644 --- a//amazon-mq/latest/developer-guide/troubleshooting-activemq.md +++ b//amazon-mq/latest/developer-guide/troubleshooting-activemq.md @@ -60 +60 @@ To resolve this issue, we recommend resolving your XA transactions with either a -If your broker is in the `RUNNING` status and some clients are able to connect to the broker successfully, while others are unable to do so, you may have reached the [wire-level connections](./amazon-mq-limits.html#broker-limits) limit for the broker. To verify that you've reached the wire-level connections limit, do the following: +If your broker is in the `RUNNING` status and some clients are able to connect to the broker successfully, while others are unable to do so, you may have reached the connection limit for the broker. For ActiveMQ brokers, this is the [wire-level connections](./amazon-mq-limits.html#broker-limits) limit. For RabbitMQ brokers, this is the per-node connection limit determined by the broker's instance type (see [Amazon MQ for RabbitMQ sizing guidelines](./rabbitmq-sizing-guidelines.html)). To verify that you've reached the connection limit, do the following: @@ -62 +62,3 @@ If your broker is in the `RUNNING` status and some clients are able to connect t - * Check the _general_ broker logs for your ActiveMQ on Amazon MQ broker in CloudWatch Logs. If the limit has been reached, you will see `Reached Maximum Connections` in the broker logs. For more information on CloudWatch Logs for ActiveMQ on Amazon MQ brokers, see [Understanding the structure of logging in CloudWatch Logs](./configure-logging-monitoring-activemq.html#security-logging-monitoring-configure-cloudwatch-structure). + * **ActiveMQ:** Check the _general_ broker logs for your ActiveMQ on Amazon MQ broker in CloudWatch Logs. If the limit has been reached, you will see `Reached Maximum Connections` in the broker logs. For more information on CloudWatch Logs for ActiveMQ on Amazon MQ brokers, see [Understanding the structure of logging in CloudWatch Logs](./configure-logging-monitoring-activemq.html#security-logging-monitoring-configure-cloudwatch-structure). + + * **RabbitMQ:** Check the `ConnectionCount` CloudWatch metric for your broker. If the value equals the maximum connections for your instance type, the limit has been reached. You can also check the RabbitMQ web console _Connections_ page to see the current connection count per node.