AWS amazon-mq medium security documentation change
Summary
Removed recommendation about creating internal users for testing authentication configurations
Security assessment
Removal from security reference guide confirms pattern of deprecating internal user testing. This change in security documentation suggests potential risks in the previous approach.
Diff
diff --git a/amazon-mq/latest/developer-guide/security-broker-auth-ref.md b/amazon-mq/latest/developer-guide/security-broker-auth-ref.md index d8d0b61e3..93d5f45a9 100644 --- a//amazon-mq/latest/developer-guide/security-broker-auth-ref.md +++ b//amazon-mq/latest/developer-guide/security-broker-auth-ref.md @@ -57,2 +56,0 @@ RabbitMQ supports multiple authentication and authorization methods to be used s -Amazon MQ recommends creating an internal user when testing authentication configurations. This allows access configuration to be validated using RabbitMQ management API. For more information, see [Access validation](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/arn-support-rabbitmq-configuration.html#access-validation). -