Amazon MQ now supports LDAP (Lightweight Directory Access Protocol) authentication for RabbitMQ brokers in all available AWS regions. This feature enables RabbitMQ brokers to authenticate and authorize Amazon MQ users using identity providers which support LDAP, providing enhanced security and flexibility in access management. You can now authenticate your Amazon MQ users through the credentials stored in your LDAP server. You can also add, delete, and modify Amazon MQ users and assign permissions to topics and queues. You can configure LDAP authentication and authorization on your RabbitMQ broker on Amazon MQ using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). To get started, create a new RabbitMQ broker with LDAP authentication or update your existing broker's configuration to enable LDAP support. This feature maintains compatibility with standard RabbitMQ LDAP implementations, ensuring seamless migration for existing LDAP enabled brokers. For detailed configuration options and steps, refer to the Amazon MQ documentation page.

Amazon MQ is now available in two new regions, Asia Pacific (Thailand) and Mexico (Central). With this launch, Amazon MQ is now available in a total of 36 regions. Amazon MQ is a managed message broker service for open-source Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers for you. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite code. For more information, please visit the https://aws.amazon.com/amazon-mq/, and see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ for complete regional availability.

Amazon MQ is now available in the AWS Asia Pacific (Malaysia) region. With this launch, Amazon MQ is now available in 34 regions. Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite or modify your applications. For more information, please visit the https://aws.amazon.com/amazon-mq/, and see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ for complete regional availability.

Amazon MQ now supports OAuth 2.0 authentication and authorization for RabbitMQ brokers with public identity providers in both single instance and highly available Multi-AZ cluster deployments. This feature enables RabbitMQ brokers to authenticate clients and users using JWT-encoded OAuth 2.0 access tokens, providing enhanced security and flexibility in access management. You can configure OAuth 2.0 on your RabbitMQ broker on Amazon MQ using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). This feature is available in all AWS regions where Amazon MQ is available. To get started, create a new RabbitMQ broker with OAuth 2.0 authentication or update your existing broker's configuration to enable OAuth2.0 support. This feature maintains compatibility with standard RabbitMQ OAuth 2.0 implementations, ensuring seamless migration for existing OAuth 2.0 enabled brokers. For detailed configuration options and steps, refer to the Amazon MQ documentation page.

https://aws.amazon.com/amazon-mq/ now supports OAuth 2.0 authentication and authorization for RabbitMQ brokers with public identity providers in both single instance and highly available Multi-AZ cluster deployments. This feature enables RabbitMQ brokers to authenticate clients and users using JWT-encoded OAuth 2.0 access tokens, providing enhanced security and flexibility in access management. You can configure OAuth 2.0 on your RabbitMQ broker on Amazon MQ using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). This feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ is available. To get started, create a new RabbitMQ broker with OAuth 2.0 authentication or update your existing broker's configuration to enable OAuth2.0 support. This feature maintains compatibility with standard RabbitMQ OAuth 2.0 implementations, ensuring seamless migration for existing OAuth 2.0 enabled brokers. For detailed configuration options and steps, refer to the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/oauth-for-amq-for-rabbitmq.html. 

This post is written by Paras Jain, Senior Technical Account Manager and Vinodh Kannan Sadayamuthu, Senior Specialist Solutions Architect This post describes the transactional capabilities of the Acti...

Amazon MQ now supports https://docs.aws.amazon.com/redshift/latest/mgmt/security-private-link.html (interface VPC endpoint) to connect directly to the Amazon MQ API in your virtual private cloud (VPC) instead of connecting over the internet. When you use AWS PrivateLink, communication between your VPC and Amazon MQ API is conducted entirely within the AWS network, providing an optimized secure pathway for your data. An AWS PrivateLink endpoint connects your VPC directly to the Amazon MQ API. The instances in your VPC don't need public IP addresses to communicate with the Amazon MQ API. To use Amazon MQ through your VPC, you can connect from an instance that is inside your VPC, or connect your private network to your VPC by using an AWS VPN option or AWS Direct Connect. You can create an AWS PrivateLink to connect to Amazon MQ using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands. To learn more about using AWS PrivateLink, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/connect-to-amazonmq.html, https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpce-interface.html#create-interface-endpoint, and the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html.

Amazon MQ is now available in two new regions, Asia Pacific (Thailand) and Mexico (Central). With this launch, Amazon MQ is now available in a total of 36 regions. Amazon MQ is a managed message broker service for open-source Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers for you. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite code. For more information, please visit the Amazon MQ product page, and see the AWS Region Table for complete regional availability.

Amazon MQ is now available in the AWS Asia Pacific (Malaysia) region. With this launch, Amazon MQ is now available in 34 regions. Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite or modify your applications. For more information, please visit the Amazon MQ product page, and see the AWS Region Table for complete regional availability.

Amazon MQ is now available in the AWS Asia Pacific (New Zealand) Region with three Availability Zones and API name ap-southeast-6. With this launch, Amazon MQ is now available in a total of 38 regions. Amazon MQ is a managed message broker service for open-source Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers for you. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite code. For more information, please visit the https://aws.amazon.com/amazon-mq/, and see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ for complete regional availability.

Amazon MQ is now available in the AWS Asia Pacific (New Zealand) Region with three Availability Zones and API name ap-southeast-6. With this launch, Amazon MQ is now available in a total of 38 regions. Amazon MQ is a managed message broker service for open-source Apache ActiveMQ and RabbitMQ that makes it easier to set up and operate message brokers on AWS. Amazon MQ reduces your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers for you. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can more easily migrate to AWS without having to rewrite code. For more information, please visit the Amazon MQ product page, and see the AWS Region Table for complete regional availability.

https://aws.amazon.com/amazon-mq/ now supports LDAP (Lightweight Directory Access Protocol) authentication for RabbitMQ brokers in all available AWS https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. This feature enables RabbitMQ brokers to authenticate and authorize Amazon MQ users using identity providers which support LDAP, providing enhanced security and flexibility in access management. You can now authenticate your Amazon MQ users through the credentials stored in your LDAP server. You can also add, delete, and modify Amazon MQ users and assign permissions to topics and queues. You can configure LDAP authentication and authorization on your RabbitMQ broker on Amazon MQ using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). To get started, create a new RabbitMQ broker with LDAP authentication or update your existing broker's configuration to enable LDAP support. This feature maintains compatibility with standard RabbitMQ LDAP implementations, ensuring seamless migration for existing LDAP enabled brokers. For detailed configuration options and steps, refer to the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/ldap-for-amq-for-rabbitmq.html. 

Discover more about what's new at AWS with Amazon MQ now supports AWS PrivateLink

更新日初回AmazonMQこれ何オープンソースメッセージブローカーApacheActiveMQorRabbitMQのAWSによるマネージドサービス

Amazon MQ now supports AWS PrivateLink (interface VPC endpoint) to connect directly to the Amazon MQ API in your virtual private cloud (VPC) instead of connecting over the internet. When you use AWS PrivateLink, communication between your VPC and Amazon MQ API is conducted entirely within the AWS network, providing an optimized secure pathway for your data. An AWS PrivateLink endpoint connects your VPC directly to the Amazon MQ API. The instances in your VPC don't need public IP addresses to communicate with the Amazon MQ API. To use Amazon MQ through your VPC, you can connect from an instance that is inside your VPC, or connect your private network to your VPC by using an AWS VPN option or AWS Direct Connect. You can create an AWS PrivateLink to connect to Amazon MQ using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands. To learn more about using AWS PrivateLink, see the Amazon MQ developer guide, Creating an Interface Endpoint, and the Amazon MQ release notes.