Deployment methods
Concert, Concert Workflows, and Concert Data Apps are available as a software-as-a-service (SaaS) or as an on-premises solution by deploying to a virtual machine (VM) or deploying to a Kubernetes cluster using Red Hat® OpenShift® Container Platform or Amazon Elastic Kubernetes Service (EKS).
Method 1: SaaS deployment
You can use IBM SaaS Console to provision and manage a SaaS instance of Concert, manage instance-level access for users and user groups, manage service IDs and more. Refer to Provisioning a SaaS instance of Concert, Workflows, and Data Apps for details.
Method 2: On-premises deployment to OpenShift Container Platform
For a lighter weight containerized solution, deploy Concert software by using OpenShift Container Platform (OCP) without IBM Cloud Pak® foundational services. When deployed, Concert uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider.
Method 3: On-premises deployment to Amazon Elastic Kubernetes Service (EKS)
Amazon Elastic Kubernetes Service (EKS) provides a lightweight container deployment option on an AWS cloud or an on-premises data center. When deployed, Concert uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider.
Method 4: On-premises deployment to a virtual machine (VM)
Deploy Concert, Concert Workflows, and Concert Data Apps software on a virtual machine (VM) in an isolated environment. When deployed, Concert VM uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider. Refer to Deploying on a virtual machine (VM) for details.
Add details about CaaS deployment.