Supported options on Amazon Web Services (AWS)

Supported installation and storage options for running IBM Cloud Pak for Integration on Amazon Web Services (AWS).

Installation options

A cluster deployed manually, using Installer Provisioned Infrastructure or User Provisioned Infrastructure. See Preparing a cluster to use Red Hat OpenShift Service on AWS (ROSA) for more information.
A managed OpenShift cluster from a cloud provider, including:
- Red Hat OpenShift Service on AWS.
- IBM Cloud Satellite. See Getting started with IBM Cloud Satellite for more information.

For versions of OpenShift Container Platform that are compatible with the Cloud Pak for Integration release, see Operating environment. For more information about the schedule for OpenShift Container Platform versions supported by OpenShift on AWS, see "Life cycle dates" in Red Hat OpenShift Service on AWS update life cycle.

Storage

The following table describes each capability's compatibility with these storage options:

Amazon Elastic Block Store (EBS)
Amazon Elastic File System (EFS)
OpenShift Data Foundation (ODF, formerly OpenShift Container Storage)
- For OpenShift Data Foundation in a production environment, the optimal minimum deployment is 4 storage nodes, with 3 Object Storage Daemons (OSDs) on each node. This provides much greater data resiliency in the event of any OSD failures.
  Important: ODF is not supported on ROSA (Red Hat OpenShift on AWS managed cloud). For more information, see OCS/ODF support on OSD and ROSA.
Portworx

Tip: When running Cloud Pak for Integration in AWS, using EBS (for RWO volumes) and EFS (for RWX) may provide the best performance and most cost-effective solution. Because RWO-based Cloud Pak for Integration capabilities provide built-in replication, it is not necessary to use a cross-availability zone (AZ) replicated RWO storage provider (such as ODF, Portworx, or IBM Storage Fusion). In addition, using these storage providers in AWS can result in substantial additional costs for network data transfer between AZs, as well as reduced performance that is caused by unnecessary data replication.

Important: When installing any capability, also refer to the requirements for Cloud Pak foundational services (at the end of this table), which are automatically installed when capabilities are created. Because the installation process for Cloud Pak foundational services automatically selects the default storage class for your cluster (which is set in OpenShift by an administrator), you must confirm that default storage class also matches the requirements for Cloud Pak foundational services.

Integration capability	AWS EBS (RWO)	AWS S3 (object storage)	AWS EFS (RWX)	OpenShift Data Foundation	Portworx
Platform UI	Yes *	N/A	Yes	Yes	Yes
Asset sharing and reuse (Automation assets)	Yes	N/A	Yes	Yes	Yes
API management (API Connect)	Yes	N/A	No	Yes	Yes
Event Endpoint Management	Yes	N/A	No	Yes	Yes
Application integration dashboard (App Connect Dashboard)	No	Yes	Yes	Yes	Yes
Application integration server (App Connect)	N/A	N/A	N/A	N/A	N/A
Application integration designer (App Connect Designer)	Yes	Yes (AI feature only)	Yes	Yes	Yes
High-speed transfer server (Aspera HSTS)	No	N/A	Yes	Yes	No
Event streams	Yes	N/A	No	Yes, block storage only	Yes
Messaging (MQ), single-instance	Yes	N/A	Yes **	Yes	Yes
Messaging (MQ), native HA	Yes	N/A	Yes **	Yes	Yes
Messaging (MQ), multi-instance	No	N/A	Yes **	Yes	Yes
Gateway (DataPower Gateway)	N/A	N/A	N/A	N/A	N/A
Cloud Pak foundational services (monitoring, licensing, managing users)	Yes	N/A	No	Yes	Yes

* Only compatible with RWO when following the instructions on Deploying the Platform UI with RWO storage

** Subject to locking considerations