AWS amazon-mq documentation change
Summary
Fixed anchor link syntax and updated a reference from 'rabbitmq-defaults.html' to 'rabbitmq-resource-limits-configuration.html' in a troubleshooting section.
Security assessment
The changes correct documentation links and anchors but do not introduce or modify security-related content. The updated resource limit reference improves accuracy but does not directly address a security issue.
Diff
diff --git a/amazon-mq/latest/developer-guide/general.md b/amazon-mq/latest/developer-guide/general.md index 1689b1bbf..179e6ec07 100644 --- a//amazon-mq/latest/developer-guide/general.md +++ b//amazon-mq/latest/developer-guide/general.md @@ -19 +19 @@ Use the information in this section to help you diagnose common issues you might - * [My broker restarted and I'm not sure why.](./general.html#w194aac39b9c13) + * [My broker restarted and I'm not sure why.](./general.html#w2aac39b9c13) @@ -161 +161 @@ The telnet connection will close automatically after a few seconds. - * If the `telnet` command succeeds, check the [ConnectionCount](./rabbitmq-logging-monitoring.html#security-logging-monitoring-cloudwatch-metrics-rabbitmq) metric and confirm that the broker has not reached the value set in the [max-connections](./rabbitmq-defaults.html#rabbitmq-defaults-values) default policy. You can also confirm if the limit has been reached by reviewing the broker `Connection.log` log group. If this metric is greater than zero, there is at least one client currently connected to the broker. If the metric shows zero connections, then perform the `telnet` path test again. You may need to repeat this process if the connection closes before your broker has published new connection metrics to CloudWatch. Metrics are published every minute. + * If the `telnet` command succeeds, check the [ConnectionCount](./rabbitmq-logging-monitoring.html#security-logging-monitoring-cloudwatch-metrics-rabbitmq) metric and confirm that the broker has not reached the value set in the [max-connections](./rabbitmq-resource-limits-configuration.html) default policy. You can also confirm if the limit has been reached by reviewing the broker `Connection.log` log group. If this metric is greater than zero, there is at least one client currently connected to the broker. If the metric shows zero connections, then perform the `telnet` path test again. You may need to repeat this process if the connection closes before your broker has published new connection metrics to CloudWatch. Metrics are published every minute.