AWS amazon-mq documentation change
Summary
Added JMS topic exchange support for RabbitMQ 4.2+ and updated version requirements for SSL/HTTP authentication features
Security assessment
Adds non-security feature documentation (JMS) and clarifies version requirements for existing security features. No evidence of vulnerability fixes or security incidents addressed.
Diff
diff --git a/amazon-mq/latest/developer-guide/amazon-mq-release-notes.md b/amazon-mq/latest/developer-guide/amazon-mq-release-notes.md index db98e07a2..eac5c0a1e 100644 --- a//amazon-mq/latest/developer-guide/amazon-mq-release-notes.md +++ b//amazon-mq/latest/developer-guide/amazon-mq-release-notes.md @@ -11,2 +11,10 @@ Date | Documentation Update -January 8, 2026 | Amazon MQ now supports SSL certificate authentication for RabbitMQ brokers using X.509 client certificates, and mutual TLS (mTLS) configuration. You can configure SSL certificate authentication and mTLS through AWS Management Console, AWS CloudFormation, AWS CLI, or AWS CDK in all AWS Regions where Amazon MQ is available. For more information, see [SSL certificate authentication](./ssl-for-amq-for-rabbitmq.html) and [Configuring mTLS](./configure-mtls.html). -January 6, 2026 | Amazon MQ now supports HTTP authentication and authorization for RabbitMQ brokers with external HTTP servers. You can configure HTTP authentication through AWS Management Console, AWS CloudFormation, AWS CLI, or AWS CDK in all AWS Regions where Amazon MQ is available. For more information, see [HTTP authentication and authorization](./http-for-amq-for-rabbitmq.html). +January 22, 2026 | Amazon MQ now supports JMS topic exchange plugin for brokers on RabbitMQ 4.2 and above. You can use the official [RabbitMQ JMS client](https://www.rabbitmq.com/client-libraries/jms-client) to run JMS workloads on Amazon MQ for RabbitMQ broker. It supports JMS 1.1, 2.0 and 3.1. For more information, see + + * [Official JMS 2.0 spec (backward compatible with and extended JMS 1.1)](https://javaee.github.io/jms-spec/pages/JMS20FinalRelease#reference-implementation) + * [Official JMS 3.1 spec](https://jakarta.ee/specifications/messaging/3.1/) + * [Limitation of RabbitMQ JMS client](https://rabbitmq.github.io/rabbitmq-jms-client/2.x/stable/htmlsingle/index.html#limitations) + * [Connecting your JMS application to Amazon MQ for RabbitMQ broker](./rabbitmq-tutorial-jms.html) + + +January 8, 2026 | Amazon MQ now supports SSL certificate authentication for brokers on RabbitMQ 4.2 and above using X.509 client certificates, and mutual TLS (mTLS) configuration. You can configure SSL certificate authentication and mTLS through AWS Management Console, AWS CloudFormation, AWS CLI, or AWS CDK in all AWS Regions where Amazon MQ is available. For more information, see [SSL certificate authentication](./ssl-for-amq-for-rabbitmq.html) and [Configuring mTLS](./configure-mtls.html). +January 6, 2026 | Amazon MQ now supports HTTP authentication and authorization for brokers on RabbitMQ 4.2 and above with external HTTP servers. You can configure HTTP authentication through AWS Management Console, AWS CloudFormation, AWS CLI, or AWS CDK in all AWS Regions where Amazon MQ is available. For more information, see [HTTP authentication and authorization](./http-for-amq-for-rabbitmq.html).