Amazon MQ for RabbitMQ now supports RabbitMQ 4.2, enterprise authentication, JMS, and Prometheus metrics in the Amazon Web Services China Regions
Amazon MQ for RabbitMQ now supports engine version 4.2 and six new capabilities in the Amazon Web Services China (Beijing) Region, operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, operated by NWCD.
With this launch, customers gain access to:
- RabbitMQ 4.2 - the Khepri metadata store for improved cluster stability, native AMQP 1.0 protocol support, and Graviton3 (m7g) instances for better price-performance.
- LDAP authentication - authenticate and authorize RabbitMQ broker connections against existing LDAP or Active Directory servers for centralized identity management.
- HTTP-based authentication - authenticate broker connections against a custom HTTP endpoint, enabling integration with OAuth 2.0 token validation services and internal identity providers.
- mTLS/X.509 certificate authentication - authenticate client connections using X.509 certificates for strong identity verification without passwords.
- JMS API support - use standard Java Message Service messaging patterns including topics, durable subscriptions, and message selectors with managed RabbitMQ brokers.
- Prometheus metrics - scrape native Prometheus-format metrics from your broker for deeper observability and integration with existing monitoring stacks.
These features enable customers in regulated industries to integrate Amazon MQ with their existing enterprise identity management systems and monitoring infrastructure.
To get started, create a new RabbitMQ broker with engine version 4.2, or upgrade your existing broker. See the Amazon MQ documentation.