Configuration and deployment user guides

Camunda 8 Self-Managed is highly customizable and can be deployed in different setups. This section highlights various use cases and scenarios of configuring Camunda 8 beyond the default values.

Each guide is considered complete and a standalone use case. However, view the deploying Camunda 8 using Helm charts page, as this is the base for all guides.

📄️ Accessing components without Ingress

Accessing Camunda 8 components externally without Ingress

📄️ Combined and separated Ingress setup

Camunda 8 Self-Managed combined and separated Ingress setup

📄️ Using existing Keycloak

Learn how to use an existing Keycloak instance in Camunda 8 Self-Managed deployment.

📄️ Using existing Elasticsearch

Learn how to use an existing Elasticsearch instance in Camunda 8 Self-Managed Helm chart deployment.

📄️ Using AWS managed OpenSearch

Learn how to use an AWS managed OpenSearch instance in Camunda 8 Self-Managed deployment.

📄️ Connect to an OpenID Connect provider

To enable a smoother integration with your existing systems, connect to an OpenID Connect provider

📄️ Installing in an air-gapped environment

Camunda 8 Self-Managed installation in an air-gapped environment

📄️ Running custom Connectors

Run custom Connectors in your Helm Kubernetes cluster.

📄️ Multi-namespace deployment

Deploy Camunda 8 Self-Managed across several namespaces for better resource management and environment separation.

📄️ Verifying Camunda 8 installation with a demo app

Ensure your installation is functioning properly by learning how to install the payment example process application on Camunda 8 Self-Managed.