AWS Security ChangesHomeSearch

AWS amazon-mq high security documentation change

Service: amazon-mq · 2026-05-16 · Security-related high

File: amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.md

Summary

Removed 'Access validation' section and related troubleshooting API documentation

Security assessment

Deletion of entire section describing ARN validation API suggests deprecation of a security validation mechanism. Removal of troubleshooting methods for role assumption and ARN resolution indicates potential security concerns with this endpoint.

Diff

diff --git a/amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.md b/amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.md
index 3d1cd01e9..e0845364b 100644
--- a//amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.md
+++ b//amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.md
@@ -7 +7 @@
-Supported keysIAM policy samplesAccess validationRelated broker quarantine statesExample scenario
+Supported keysIAM policy samplesRelated broker quarantine statesExample scenario
@@ -34,2 +33,0 @@ Amazon MQ for RabbitMQ supports AWS ARNs for the values of some RabbitMQ configu
-  * Access validation
-
@@ -84,12 +81,0 @@ See [Using LDAP authentication and authorization](./rabbitmq-ldap-tutorial.html)
-## Access validation
-
-To troubleshoot scenarios where ARN values cannot be fetched, the aws plugin supports a [RabbitMQ management API endpoint](https://github.com/amazon-mq/rabbitmq-aws/blob/main/API.md) that can be called to check if Amazon MQ is able to successfully assume the role and resolve AWS ARNs. This avoids the need to update broker configuration, update broker with the new configuration revision and reboot broker to test configuration changes.
-
-###### Note
-
-Use of this API requires an existing RabbitMQ administrator user. Amazon MQ recommends creating test brokers with an internal user in addition to other access methods. See [enabling both OAuth 2.0 and simple (internal) authentication](./oauth-tutorial.html#oauth-tutorial-config-both-auth-methods-using-cli). This user can then be used to access the validation API.
-
-###### Note
-
-Though aws plugin supports passing a new role as an input to the validation API, this parameter is not supported by Amazon MQ. The IAM role used for validation should match the value of `aws.arns.assume_role_arn` in broker configuration.
-
@@ -125,4 +110,0 @@ Additionally, the broker will enter the `INVALID_ASSUMEROLE` quarantine state. F
-  * Call the validation endpoint to verify if RabbitMQ is now able to access the secret:
-    
-        curl -4su 'guest:guest' -XPUT -H 'content-type: application/json' <broker-endpoint>/api/aws/arn/validate -d '{"assume_role_arn":"arn:aws:iam::<account-id>:role/<role-name>","arns":["arn:aws:secretsmanager:<region>:<account-id>:secret:<secret-name>"]}' | jq '.'
-