Amazon MQ now supports ActiveMQ minor version 5.19 Amazon MQ now supports ActiveMQ minor version 5.19, which introduces several improvements and fixes compared to the previous version of ActiveMQ supported by Amazon MQ. Amazon MQ manages the patch version upgrades for your brokers. All brokers on ActiveMQ version 5.19 will be automatically upgraded to the next compatible and secure patch version in your scheduled maintenance window. If you are utilizing prior versions of ActiveMQ, such as 5.18, we strongly recommend you to upgrade to ActiveMQ 5.19. You can easily perform this upgrade with just a few clicks in the AWS Management Console. To learn more about upgrading, consult the ActiveMQ Version Management section in the Amazon MQ Developer Guide. To learn more about the changes in ActiveMQ 5.19, see the Amazon MQ release notes. This version is available across all AWS Regions where Amazon MQ is available.

🆕 Amazon MQ now supports ActiveMQ 5.19, offering improvements and fixes. It automatically upgrades brokers to secure patch versions. Upgrade from 5.18 via AWS Console; see Amazon MQ Developer Guide for details. Available in all AWS Regions.

#AWS #AmazonMq

Amazon MQ now supports ActiveMQ minor version 5.19 Amazon MQ now supports ActiveMQ minor version 5.19, which introduces several improvements and fixes compared to the previous version of ActiveMQ supported by Amazon MQ. Amazon MQ manages the patch version upgrades for your brokers. All brokers on ActiveMQ version 5.19 will be automatically upgraded to the next compatible and secure patch version in your scheduled maintenance window. If you are utilizing prior versions of ActiveMQ, such as 5.18, we strongly recommend you to upgrade to ActiveMQ 5.19. You can easily perform this upgrade with just a few clicks in the AWS Management Console. To learn more about upgrading, consult the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/activemq-version-management.htmlin the Amazon MQ Developer Guide. To learn more about the changes in ActiveMQ 5.19, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html. This version is available across all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ is available.

Amazon MQ now supports ActiveMQ minor version 5.19

Amazon MQ now supports ActiveMQ minor version 5.19, which introduces several improvements and fixes compared to the previous version of ActiveMQ supported by Amazon MQ. Amazon MQ manages the patch version upgrades for your brok...

#AWS #AmazonMq

Amazon MQ now supports Java Messaging Service (JMS) specification for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ 4 brokers to connect to JMS applications through the RabbitMQ JMS Topic Exchange plugin and https://www.rabbitmq.com/client-libraries/jms-client. The JMS topic exchange plugin is enabled by default on all RabbitMQ 4 brokers, allowing you to use the JMS client to run your JMS 1.1, JMS 2.0, and JMS 3.1 applications on RabbitMQ. You can also use the RabbitMQ JMS client to send JMS messages to an AMQP exchange and consume messages from an AMQP queue to interoperate or migrate JMS workloads to AMQP workloads. To start using your JMS applications on RabbitMQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then use the RabbitMQ JMS client to connect your applications. To learn more about the plugin, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html and the Amazon MQ https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/working-with-rabbitmq.html. This plugin is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ RabbitMQ 4 instances are available today. 

Amazon MQ now supports Java Messaging Service (JMS) specification for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ 4 brokers to connect to JMS applications through the RabbitMQ JMS Topic Exchange plugin and https://www.rabbitmq.com/client-libraries/jms-clien

#AWS #AmazonMq

Amazon MQ now supports Java Messaging Service (JMS) specification for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ 4 brokers to connect to JMS applications through the RabbitMQ JMS Topic Exchange plugin and JMS client. The JMS topic exchange plugin is enabled by default on all RabbitMQ 4 brokers, allowing you to use the JMS client to run your JMS 1.1, JMS 2.0, and JMS 3.1 applications on RabbitMQ. You can also use the RabbitMQ JMS client to send JMS messages to an AMQP exchange and consume messages from an AMQP queue to interoperate or migrate JMS workloads to AMQP workloads. To start using your JMS applications on RabbitMQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then use the RabbitMQ JMS client to connect your applications. To learn more about the plugin, see the Amazon MQ release notes and the Amazon MQ developer guide. This plugin is available in all regions where Amazon MQ RabbitMQ 4 instances are available today.

🆕 Amazon MQ now supports JMS for RabbitMQ 4 brokers, enabling JMS 1.1-3.1 apps via the JMS Topic Exchange plugin. Select RabbitMQ 4.2 on M7g to use the RabbitMQ JMS client for JMS to AMQP interoperability. Available in all regions with Amazon MQ RabbitMQ 4.

#AWS #AmazonMq

Amazon MQ now supports certificate based authentication with mutual TLS for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) using X.509 client certificates with mutual TLS (mTLS). The RabbitMQ auth_mechanism_ssl plugin can be configured on brokers running RabbitMQ version 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using certificate based authentication on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file with the required https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/configurable-values.html. To learn more about the plugin, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html and the Amazon MQ https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/working-with-rabbitmq.html. This plugin is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ RabbitMQ 4 instances are available today. 

Amazon MQ now supports certificate based authentication with mutual TLS for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) using X.509 client certificates with mutual TLS (mTLS). The RabbitMQ auth_...

#AWS #AmazonMq

Amazon MQ now supports certificate based authentication with mutual TLS for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) using X.509 client certificates with mutual TLS (mTLS). The RabbitMQ auth_mechanism_ssl plugin can be configured on brokers running RabbitMQ version 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using certificate based authentication on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file with the required values. To learn more about the plugin, see the Amazon MQ release notes and the Amazon MQ developer guide. This plugin is available in all regions where Amazon MQ RabbitMQ 4 instances are available today.

🆕 Amazon MQ supports RabbitMQ brokers with X.509 client certs for mutual TLS auth via the RabbitMQ auth_mechanism_ssl plugin on version 4.2+ brokers. Create a broker using M7g instance type in AWS console, CLI, or SDKs. Available in all regions with RabbitMQ 4.

#AWS #AmazonMq

Amazon MQ now supports HTTP based authentication for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) and authorization (determining what permissions they have) by making requests to an HTTP server. This plugin can be configured on brokers running RabbitMQ 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using HTTP based authentication and authorization on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the m7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file. To learn more about the plugin, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html and the Amazon MQ https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/working-with-rabbitmq.html. This plugin is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ RabbitMQ 4 instances are available today. 

Amazon MQ now supports HTTP based authentication for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) and authorization (determining what permissions they have) by making requests to an HTTP server. ...

#AWS #AmazonMq

Amazon MQ now supports HTTP based authentication for RabbitMQ brokers Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) and authorization (determining what permissions they have) by making requests to an HTTP server. This plugin can be configured on brokers running RabbitMQ 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using HTTP based authentication and authorization on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the m7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file. To learn more about the plugin, see the Amazon MQ release notes and the Amazon MQ developer guide. This plugin is available in all regions where Amazon MQ RabbitMQ 4 instances are available today.

🆕 Amazon MQ now supports HTTP-based authentication for RabbitMQ brokers, enabling authentication and authorization via HTTP requests. Available for RabbitMQ 4.2+ on Amazon MQ, configure via the associated config file. Available in all regions with Amazon MQ RabbitMQ 4 instances.

#AWS #AmazonMq

Amazon MQ now supports RabbitMQ version 4.2 Amazon MQ now supports RabbitMQ version 4.2 which introduces native support for the AMQP 1.0 protocol, a new Raft based metadata store named Khepri, local shovels, and message priorities for quorum queues. RabbitMQ 4.2 also includes various bug fixes and performance improvements for throughput and memory management. A key highlight of RabbitMQ 4.2 is the support of AMQP 1.0 as a core protocol offering enhanced features like modified outcome which allow consumers to modify message annotations before requeueing or dead lettering, and granular flow control, which offers benefits including letting a client application dynamically adjust how many messages it wants to receive from a specific queue. Amazon MQ has also introduced configurable resource limits for RabbitMQ 4.2 brokers which you can modify based on your application requirements. Starting from RabbitMQ 4.0, mirroring of classic queues is no longer supported. Non-replicated classic queues are still supported. Quorum queues are the only replicated and durable queue type supported on RabbitMQ 4.2 brokers, and now offer message priorities in addition to consumer priorities. To start using RabbitMQ 4.2 on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the m7g instance type through the AWS Management console, AWS CLI, or AWS SDKs. Amazon MQ automatically manages patch version upgrades for your RabbitMQ 4.2 brokers, so you need to only specify the major.minor version. To learn more about the changes in RabbitMQ 4.2, see the https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-release-notes.html and the Amazon MQ https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/working-with-rabbitmq.html. This version is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon MQ m7g type instances are available today. 

Amazon MQ now supports RabbitMQ version 4.2

Amazon MQ now supports RabbitMQ version 4.2 which introduces native support for the AMQP 1.0 protocol, a new Raft based metadata store named Khepri, local shovels, and message priorities for quorum queues. RabbitMQ 4.2 also includes v...

#AWS #AmazonMq

Amazon MQ now supports RabbitMQ version 4.2 Amazon MQ now supports RabbitMQ version 4.2 which introduces native support for the AMQP 1.0 protocol, a new Raft based metadata store named Khepri, local shovels, and message priorities for quorum queues. RabbitMQ 4.2 also includes various bug fixes and performance improvements for throughput and memory management. A key highlight of RabbitMQ 4.2 is the support of AMQP 1.0 as a core protocol offering enhanced features like modified outcome which allow consumers to modify message annotations before requeueing or dead lettering, and granular flow control, which offers benefits including letting a client application dynamically adjust how many messages it wants to receive from a specific queue. Amazon MQ has also introduced configurable resource limits for RabbitMQ 4.2 brokers which you can modify based on your application requirements. Starting from RabbitMQ 4.0, mirroring of classic queues is no longer supported. Non-replicated classic queues are still supported. Quorum queues are the only replicated and durable queue type supported on RabbitMQ 4.2 brokers, and now offer message priorities in addition to consumer priorities. To start using RabbitMQ 4.2 on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the m7g instance type through the AWS Management console, AWS CLI, or AWS SDKs. Amazon MQ automatically manages patch version upgrades for your RabbitMQ 4.2 brokers, so you need to only specify the major.minor version. To learn more about the changes in RabbitMQ 4.2, see the Amazon MQ release notes and the Amazon MQ developer guide. This version is available in all regions where Amazon MQ m7g type instances are available today.

🆕 Amazon MQ now supports RabbitMQ 4.2 with AMQP 1.0, Khepri metadata store, local shovels, message priorities, and configurable resource limits. Available in all regions with m7g instances.

#AWS #AmazonMq

Amazon MQ now supports LDAP authentication for RabbitMQ 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. 

Amazon MQ now supports LDAP authentication for RabbitMQ

https://aws.amazon.com/amazon-mq/ now supports LDAP (Lightweight Directory Access Protocol) authentication for RabbitMQ brokers in all available AWS aws.amazon.com/about-aws/global-infrast...

#AWS #AwsGovcloudUs #AmazonMq

Amazon MQ now supports LDAP authentication for RabbitMQ 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 now supports LDAP authentication for RabbitMQ, enabling enhanced security and flexibility in access management via identity providers. Configure via AWS Console, CLI, or CloudFormation. For details, see Amazon MQ documentation.

#AWS #AwsGovcloudUs #AmazonMq

Amazon MQ is now available in AWS Asia Pacific (New Zealand) Region 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 AWS Asia Pacific (New Zealand) Region

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.

Ama...

#AWS #AmazonMq

Amazon MQ is now available in AWS Asia Pacific (New Zealand) Region 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.

🆕 Amazon MQ now available in AWS Asia Pacific (New Zealand) Region with 3 zones, expanding to 38 regions. Managed service for Apache ActiveMQ and RabbitMQ, reducing operational tasks. For details, visit Amazon MQ product page.

#AWS #AmazonMq

Amazon MQ now supports OAuth 2.0 plugin for RabbitMQ 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. 

Amazon MQ now supports OAuth 2.0 plugin for RabbitMQ

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 fea...

#AWS #AmazonMq

Amazon MQ now supports OAuth 2.0 plugin for RabbitMQ 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.

🆕 Amazon MQ now supports OAuth 2.0 for RabbitMQ, enabling secure client authentication via JWT tokens in single and Multi-AZ deployments. Configure via AWS Console, CLI, or CDK. Available in all regions with Amazon MQ. For details, see Amazon MQ documentation.

#AWS #AmazonMq

Amazon MQ is now available in two additional regions 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 two additional regions

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-s...

#AWS #AmazonMq

Amazon MQ is now available in two additional regions 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 expands to Asia Pacific (Thailand) and Mexico (Central), now available in 36 regions. It's a managed service for Apache ActiveMQ and RabbitMQ, easing setup and maintenance while supporting industry-standard APIs and protocols for easy migration to AWS.

#AWS #AmazonMq

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

Amazon MQ now supports hashtag#AWS PrivateLink!
aws.amazon.com/about-aws/wh...

#messagequeue #PrivateLink #AmazonMQ #MQ

Amazon MQ now supports AWS PrivateLink 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 now supports AWS PrivateLink

Amazon MQ now supports docs.aws.amazon.com/redshift/latest/mgmt/sec... (interface VPC endpoint) to connect directly to the Amazon MQ API in your virtual private cloud (VPC) instead of connecting over the interne...

#AWS #AmazonMq

Amazon MQ now supports AWS PrivateLink 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.

🆕 Amazon MQ now supports AWS PrivateLink

#AWS #AmazonMq

Implementing transactions using JMS2.0 in Amazon MQ for ActiveMQ | Amazon Web Services 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...

AWS has just released a comprehensive guide on implementing transactions using JMS 2.0 in Amazon MQ for ActiveMQ. This is a game changer for those building robust, distributed messaging systems.

#AmazonMQ #ActiveMQ

aws.amazon.com/blogs/comput...

Amazon MQ is now available in the AWS Asia Pacific (Malaysia) region 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 is now available in the AWS Asia Pacific (Malaysia) region

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 Rabb...

#AWS #AmazonMq

Amazon MQ is now available in the AWS Asia Pacific (Malaysia) region 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 (Malaysia) region

#AWS #AmazonMq

Coming up in a a few hours on #Twitch! Tune into AWS re:Post Live ! On this episode we will be Diving Deep into #AmazonMQ. Submit your questions re:Post and join today at 11:00am PDT / 2PM EDT: twitch.tv/aws. bit.ly/3Cwyg1O