Amazon MQ Enables Certificate-Based Authentication with Mutual TLS for RabbitMQ Brokers

Amazon MQ RabbitMQ now supports client authentication using X.509 certificates with mutual TLS for enhanced security.

By Elena Parker · Editorial pseudonym · 2026-01-08 · 1 min read

AI-ASSISTED REPORTING · RETROSPECTIVE ARCHIVE

Retrospective edition: 2026-01-08. Source published: 2026-01-08. Added to this archive: 2026-11-03. This briefing was prepared later from the linked announcement; it was not published on this website on the historical edition date.

Amazon MQ RabbitMQ brokers (version 4.2+) can use the auth_mechanism_ssl plugin to enable mutual TLS authentication, validating client identities through X.509 certificates rather than traditional credentials. This adds a security layer controlling broker access.

Configuration requires editing the RabbitMQ broker’s configuration file and choosing RabbitMQ 4.2 brokers running on M7g instances. The feature is available across all AWS regions supporting RabbitMQ 4 instances, aligning with security best practices for message brokers.

takeaways:[

Source & further reading

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

Source published 2026-01-08. This report was prepared with AI assistance from the linked primary-source material. Claims and limitations should be checked against the original announcement or research.