📊Tracking: Amazon MQ

Add your +1 👍 to help us prioritize high-level constructs for this service
---

### Overview:

Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud. Message brokers allow different software systems–often using different programming languages, and on different platforms–to communicate and exchange information. Amazon MQ reduces your operational load by managing the provisioning, setup, and maintenance of ActiveMQ, a popular open-source message broker. Connecting your current applications to Amazon MQ is easy because it uses industry-standard APIs and protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. Using standards means that in most cases, there’s no need to rewrite any messaging code when you migrate to AWS.

[AWS Docs](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/welcome.html)

### Maturity: CloudFormation Resources Only

See the [AWS Construct Library Module Lifecycle doc](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) for more information about maturity levels.

### Implementation:

See the [CDK API Reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-amazonmq-readme.html) for more implementation details.

### Issue list:

---
This is a 📊Tracking Issue

Start with the AWS Docs link in the issue to understand Amazon MQ, then review the linked CDK API Reference and the construct library module lifecycle document. The issue is a tracking request for high-level constructs rather than a scoped implementation task, so the files, tests, and completion criteria are not identified.

Written by the indexing model from the issue text.