Amazon MQ for RabbitMQ adds private networking
Amazon MQ for RabbitMQ now supports private networking, allowing brokers to connect to private VPC resources without public exposure. This enhances security and compliance for integrations with services like identity providers or other brokers, eliminating previous complex workarounds. The feature uses AWS VPC Lattice, RAM, and PrivateLink and is available for RabbitMQ brokers in regions with VPC Lattice.
- →Support for private networking connectivity
- →Simplified connectivity for RabbitMQ Federation, Shovel, and authentication
- →Availability and setup requirements
Features (1) ›
- Support for private networking connectivity
Amazon MQ for RabbitMQ brokers can now connect to private resources within your VPC without requiring public exposure. This feature simplifies secure integrations with identity providers, other Amazon MQ brokers, or self-hosted RabbitMQ instances.
Enhancements (1) ›
- Simplified connectivity for RabbitMQ Federation, Shovel, and authentication
This update removes the need for workarounds involving Network Load Balancer and NAT Gateway for features like RabbitMQ Federation, Shovel, and authentication. Connectivity is now managed via Amazon VPC Lattice, AWS Resource Access Manager, and AWS PrivateLink.
Notes (1) ›
- Availability and setup requirements
Private networking is exclusively available for Amazon MQ for RabbitMQ brokers in AWS Regions supporting Amazon VPC Lattice. Initial setup involves creating a VPC Lattice resource gateway and configuring an AWS RAM resource share.
https://aws.amazon.com/about-aws/whats-new/2026/05/amazon-mq-private-network-connectivity/
Related releases
- Amazon Aurora DSQL adds multi-Region cluster support in four more Regions AWS What's New ·
- CloudWatch adds managed Prometheus collectors AWS What's New ·
- Amazon EC2 C7i Instances Expand to New Regions AWS What's New ·
- EC2 C7i-flex instances now available in Europe (Milan) region AWS What's New ·
- AWS CodeDeploy Expands to Five New Regions AWS What's New ·
- Redis 8.0 end-of-life date moved to 2026-12-01 endoflife.date ·