Migrating to AWS your existing queues and topics used for application de-coupling without rewriting your code
Start course
1h 41m

This course covers the core learning objective to meet the requirements of the 'Designing for disaster recovery & high availability in AWS - Level 2' skill

Learning Objectives:

  • Analyze the amount of resources required to implement a fault-tolerant architecture across multiple AWS availability Zones
  • Evaluate an effective AWS disaster recovery strategy to meet specific business requirements
  • Understand SLA for AWS services to ensure the high availability of a given AWS solution
  • Analyze which AWS services can be leveraged to implement a decoupled solution

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.


About the Author
Learning Paths

Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.

To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.

Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.

He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.

In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.

Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.