As the AWS Cloud continues to gain attraction and popularity, it's not unusual for existing data center applications to be already using some form of message broker. IBMMQ, TIBCO EMS, RabbitMQ, and Apache ActiveMQ have a widespread use in existing data centers across the world. As cloud adoption continues, sometimes they need to move existing applications from a local data center to AWS is required with no modification to the existing code. If you are already using messaging APIs like Java Message Service, .Net Message Service, MQ Telemetry Transport, or WebSockets, you can actually move your existing application with no code modification by using the Amazon MQ Service. Amazon MQ is AWS managed message broker service for Apache ActiveMQ, and is compliant with existing code leveraging JMS, NMS, MQTT and WebSockets.

The idea for the service is to enable you and migrate your messaging and applications without having to rewrite your code. Amazon MQ is cost-effective in that you pay for broker instance and storage as you need them. The service is automated in terms of administration and maintenance, and it's highly available in a region. The storage, like many other AWS services is implemented across multiple availability zones and you can implement active and standby configurations with automatic failover. Amazon MQ also provides message encryption in transit using SSL and at rest using AES 256 encryption. Network isolation of your message broker instance can be implemented using a private endpoint in your Amazon VPC and configuring security groups to control network accessibility. The service integrates seamlessly with Amazon CloudWatch for the monitoring of metrics on existing queues, topics, and the broker itself. It also integrates with AWS CloudTrail for log in. Consider Amazon MQ when migrating existing applications that are already using a message broker, and you want to keep your applications as they are written.