reference deployment

IBM Cloud Pak for Integration on AWS

Integration capabilities to connect applications and data

This Partner Solution provides step-by-step instructions for deploying IBM Cloud Pak for Integration on a Red Hat OpenShift Container Platform (OCP) cluster on the AWS Cloud. Cloud Pak for Integration provides a simple, complete solution that brings together IBM’s powerful integration capabilities to support a broad range of integration styles and use cases as part of your journey to the cloud.

Cloud Pak for Integration uses AWS services and features, including virtual private clouds (VPCs), Availability Zones, security groups, Amazon Elastic Block Store (Amazon EBS), Amazon Elastic Compute Cloud (EC2), and Elastic Load Balancing to build a reliable and scalable cloud platform.

IBM logo

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

  •  What you'll build
  • This Partner Solution sets up the following:

    • A highly available architecture that spans one or three Availability Zones.*
    • A 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.*
      • A boot node Amazon EC2 instance that also serves as a bastion host to allow inbound Secure Shell (SSH) access to EC2 instances in the private subnets.
    • In the private subnets:
      • Red Hat OCP master nodes in up to three Availability Zones.
      • OCP compute nodes that host the Cloud Pak for Integration capabilities.
      • Amazon EBS disks that are mounted on the compute nodes for container-persistent data.
    • A Classic Load Balancer spanning the public subnets for accessing Cloud Pak for Integration from a web browser.
    • A Classic Load Balancer spanning the public subnets for accessing the OpenShift Container Storage (OCS) S3 service.
    • A Classic Load Balancer spanning the public subnets for accessing the OCS NooBaa service.
    • A Network Load Balancer spanning the public subnets for routing external OpenShift application programming interface (API) traffic to the OCP master instances.
    • A Network Load Balancer spanning the private subnets for routing internal OpenShift API traffic to the OCP master instances.
    • Amazon Route 53 as your public Domain Name System (DNS) for resolving domain names of the Cloud Pak for Integration management console and applications deployed on the cluster.

    * The template that deploys the Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy IBM Cloud Pak for Integration on AWS, follow the instructions in the deployment guide. A standard deployment takes about 2 hours, and a high-availability (HA) deployment takes a little over 2 hours. The deployment process includes these steps:

    1. This Partner Solution requires a Red Hat OpenShift subscription. During the deployment, provide your OpenShift installer-provisioned infrastructure pull secret. To procure a 60-day evaluation license for OpenShift, follow the instructions at Evaluate Red Hat OpenShift Container Platform.
    2. Subscribe to Cloud Pak for Integration. If you don't have a paid entitlement, you can create a 60-day trial subscription key.
    3. This Partner Solution uses OpenShift Container Storage (OCS) as technology to provide persistent storage for its capabilities and runtimes. For information about licensed versions, refer to OpenShift Container Storage.
    4. If you don't already have an AWS account, sign up at, and sign in to your account.
    5. Launch the Partner Solution by choosing from the following options:
    6. (Optional) Edit the application security group.
    7. Test the deployment by using the Cloud Pak for Integration UI.
    8. Manage your cluster using the OpenShift Console.
    9. (Optional) Provide boot-node SSH access.

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

  •  Costs and licenses
  • You can get started with a 60-day trial period or use your existing Cloud Pak for Integration entitlement. You can also use an evaluation version of OpenShift Container Platform (OCP) and OpenShift Container Storage (OCS), or use your existing entitlement to those components.

    For pricing information or to use your existing Cloud Pak for Integration entitlements, contact an IBM sales representative. For more information about licensing terms, refer to the Cloud Pak for Integration software license agreement.

    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?