reference deployment

IBM MQ Native HA on AWS

Messaging platform for cloud, mobile, IoT, and on-premises environments

View deployment guide

This Partner Solution deploys IBM MQ Native HA container to an Amazon Elastic Kubernetes Service (Amazon EKS) cluster in the Amazon Web Services (AWS) Cloud.

IBM MQ is messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms. It uses message queues to facilitate the exchange of information, and offers a single messaging solution for cloud, mobile, the Internet of Things (IoT), and on-premises environments. The solution supports client messaging applications from within your virtual private cloud (VPC), from trusted addresses on the internet, and via a VPN from your on-premises environment.

This Partner Solution was developed by IBM in collaboration with AWS. IBM is an AWS Partner.

Contact partner

AWS Service Catalog administrators can add this architecture to their own catalog.  

Use in AWS Service Catalog
  •  What you'll build

  • This Partner Solution sets up the following:

    • A highly available architecture that spans three Availability Zones.
    • A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.
    • In the public subnets:
      • Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.
      • One boot node, an Amazon Elastic Compute Cloud (Amazon EC2) instance, to access the Amazon EKS cluster. 
    • In the private subnets, an Amazon EKS managed node group to automate the provisioning and lifecycle management of the nodes (Amazon EC2 instances) for the Amazon EKS cluster. Each node comprises the following:
      • An IBM MQ server.
      • An Amazon Elastic Block Store (Amazon EBS) volume for persistent distributed storage and high availability of the queue manager service and message data.
    • A Classic Load Balancer that automatically distributes connections to the active IBM MQ server.
    • Amazon EKS, which provides the Kubernetes control plane for the cluster.
  •  How to deploy

  • To deploy this Partner Solution, follow the instructions in the deployment guide, which includes these steps.

    1. Sign in to your AWS account. If you don't already have an AWS account, sign up at https://aws.amazon.com.
    2. Download and configure the Kubernetes command line interface. For more information, refer to Installing or updating kubectl.
    3. Launch the Partner Solution. The stack takes about 30 minutes to deploy. Before you create the stack, choose the AWS Region from the top toolbar. 
    4. Complete the postdeployment steps in the deployment guide.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

    View deployment guide for details
  •  Costs and licenses

  • This solution makes use of Helm charts to deploy IBM MQ Advanced for Developers container images as an IBM MQ Native HA solution on Amazon EKS.

    The IBM MQ software license agreement details the licensing terms.

    You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?