Amazon MQ for RabbitMQ now supports private networking connectivity

Amazon MQ for RabbitMQ now supports private networking, enabling your brokers to connect to private resources in your VPC without exposing those resources publicly.. This helps you meet your security and compliance requirements when your brokers need to reach private identity providers (such as LDAP and OAuth 2.0), other Amazon MQ for RabbitMQ brokers, or self-hosted RabbitMQ brokers. Previously, this connectivity for RabbitMQ Federation, Shovel, or authentication required Network Load Balancer and NAT Gateway workarounds. Amazon MQ establishes this connectivity using Amazon VPC Lattice, AWS Resource Access Manager (AWS RAM), and AWS PrivateLink, and manages the underlying infrastructure on your behalf. To get started, create a VPC Lattice resource gateway, package your resource configurations into an AWS RAM resource share, and associate it with your broker. Private networking is available only for Amazon MQ for RabbitMQ brokers, in all [AWS Regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) where [Amazon VPC Lattice](https://aws.amazon.com/vpc/lattice/) is available. To learn more, see [Private networking](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/private-networking.html) in the Amazon MQ Developer Guide and the [Amazon MQ pricing page](https://aws.amazon.com/amazon-mq/pricing/).