For the complete documentation index, see llms.txt.
Skip to main content
Version: 8.10 (unreleased)

Create a cluster

To deploy and run your process, you must create a cluster in Camunda 8.

Create a cluster

To create a cluster in SaaS:

  1. In Camunda Hub, in the left navigation under Console, click Clusters.
  2. Click Create cluster.
  3. Name your cluster.
  4. Select your region.
  5. Select a cluster type and cluster size.
  6. Assign a cluster tag to indicate what type of cluster it is.
  7. Select your encryption at rest protection level (enterprise only).
  8. Select a channel and release. For the purpose of this guide, we recommend using the Stable channel and the latest generation.
  9. If you are using a generation of version 8.8 or higher, select if you want to enable authorization-based access control.
  10. Click Create cluster.
  11. Your cluster will take a few moments to create. Check the status on the Clusters page or by clicking into the cluster itself and looking at the Applications section.

If you haven't created a cluster yet, the Clusters page will be empty. You can start modeling even if the cluster shows a Creating status.

tip

In Self-Managed, review the cluster configuration properties.

View the created cluster

After creating the cluster, you can view the new entry:

  1. In the left navigation under Console, click Clusters.
  2. The cluster is now being set up. During this phase, its state is Creating. After one or two minutes, the cluster is ready for use and changes its state to Healthy.
  3. After the cluster is created, click the cluster name to visit the cluster detail page.

Tag your cluster

You can tag your cluster for dev, test, stage, or prod:

  1. In the left navigation under Clusters, select your cluster.
  2. On the Overview tab under Cluster Details, click Modify tag.

Assigning a tag:

  • Makes it easier for team members to clearly distinguish between different stages of the software development lifecycle.
  • Has no impact on performance and can be changed later in the cluster details section of the cluster overview page.
  • Disables authorization-based access control by default for dev and test clusters, and enables it for stage and prod clusters. You can change this setting during and after cluster creation.

See clusters for more details.