AWS amazon-mq documentation change
Summary
Changed heading levels from ### to #### for authentication method sections and updated documentation links for RabbitMQ's simple authentication method
Security assessment
The changes are structural (heading hierarchy adjustments) and link updates without introducing new security content or addressing vulnerabilities. No evidence of security fixes or vulnerabilities mentioned.
Diff
diff --git a/amazon-mq/latest/developer-guide/amazon-mq-access.md b/amazon-mq/latest/developer-guide/amazon-mq-access.md index 0192307d8..8097bf506 100644 --- a//amazon-mq/latest/developer-guide/amazon-mq-access.md +++ b//amazon-mq/latest/developer-guide/amazon-mq-access.md @@ -15 +15 @@ Amazon MQ for RabbitMQ supports the following authentication and authorization m -### Simple authentication and authorization +#### Simple authentication and authorization @@ -17 +17 @@ Amazon MQ for RabbitMQ supports the following authentication and authorization m -In this method, broker users are stored internally in the RabbitMQ broker and managed through the web console or management API. Permissions for vhosts, exchanges, queues, and topics are configured directly in RabbitMQ. This is the default method. For more information about this method, see [Broker users](./rabbitmq-basic-elements-user.html). +In this method, broker users are stored internally in the RabbitMQ broker and managed through the web console or management API. Permissions for vhosts, exchanges, queues, and topics are configured directly in RabbitMQ. This is the default method. For more information, see [Simple authentication and authorization](./rabbitmq-simple-auth-broker-users.html). @@ -19 +19 @@ In this method, broker users are stored internally in the RabbitMQ broker and ma -### OAuth 2.0 authentication and authorization +#### OAuth 2.0 authentication and authorization @@ -21 +21 @@ In this method, broker users are stored internally in the RabbitMQ broker and ma -In this method, broker users and their permissions are managed by an external OAuth 2.0 identity provider (IdP). User authentication and resource permissions for vhosts, exchanges, queues, and topics are centralized through the OAuth 2.0 provider's scope system. This simplifies user management and enables integration with existing identity systems. For more information about this method, see [OAuth 2.0 authentication and authorization](./oauth-for-amq-for-rabbitmq.html). +In this method, broker users and their permissions are managed by an external OAuth 2.0 identity provider (IdP). User authentication and resource permissions for vhosts, exchanges, queues, and topics are centralized through the OAuth 2.0 provider's scope system. This simplifies user management and enables integration with existing identity systems. For more information, see [OAuth 2.0 authentication and authorization](./oauth-for-amq-for-rabbitmq.html). @@ -23 +23 @@ In this method, broker users and their permissions are managed by an external OA -### LDAP authentication and authorization +#### LDAP authentication and authorization @@ -25 +25 @@ In this method, broker users and their permissions are managed by an external OA -In this method, broker users and their permissions are managed by an external LDAP directory service. User authentication and resource permissions are centralized through the LDAP server, allowing users to access RabbitMQ using their existing directory service credentials. For more information about this method, see [LDAP authentication and authorization](./ldap-for-amq-for-rabbitmq.html). +In this method, broker users and their permissions are managed by an external LDAP directory service. User authentication and resource permissions are centralized through the LDAP server, allowing users to access RabbitMQ using their existing directory service credentials. For more information, see [LDAP authentication and authorization](./ldap-for-amq-for-rabbitmq.html). @@ -37 +37 @@ Amazon MQ for ActiveMQ supports the following authentication and authorization m -### Simple authentication and authorization +#### Simple authentication and authorization @@ -41 +41 @@ In this method, broker users are created and managed through the Amazon MQ conso -### LDAP authentication and authorization +#### LDAP authentication and authorization