Amazon MQ now supports certificate based authentication with mutual TLS for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) using X.509 client certificates with mutual TLS (mTLS). The RabbitMQ auth\_mechanism\_ssl plugin can be configured on brokers running RabbitMQ version 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using certificate based authentication on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file with the required [values](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/configurable-values.html). To learn more about the plugin, see the [Amazon MQ release notes](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html) and the Amazon MQ [developer guide](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/working-with-rabbitmq.html). This plugin is available in all [regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) where Amazon MQ RabbitMQ 4 instances are available today.