Skip to main content
Version: 8.8 (unreleased)

Overview

Camunda supports multiple storage options for handling documents in Self-Managed environments. Depending on your deployment setup and production requirements, you can choose from cloud-based, local, or in-memory storage methods.

The following section outlines supported storage options, their intended use cases, and configuration guidance.

Jump to the environment configuration options below:

note

Camunda 8 Run is a fast way for users to test the capabilities of the platform, but it is not necessarily scalable. Docker Compose is not recommended for use in production. Therefore, Helm is currently the only option to deploy the platform in a Self-Managed environment for production.

Supported storage options​

  • By using external cloud file bucket storages, documents can be stored in a secure, and scalable way. Buckets are integrated per cluster to ensure proper isolation and environment-specific management. The following file bucket storages are supported:
  • Local storage can be configured for a cluster to store documents in a local folder.
    • It can be used only for local development with Camunda 8 Run.
    • Local storage is not suitable for production use, as pods and file paths are not shared across components. This prevents components like Tasklist and Zeebe from accessing the same data. Files are stored locally, and their retention must be managed manually.
  • In-memory storage can be used to store documents during the application's runtime. When the application is stopped, documents are lost.
    • It can be used with Camunda 8 Run, Docker Compose and Helm.
    • In-memory storage is not suitable for production use, as pods and memory are not shared across components. Files stored in memory are not persisted and will be lost on application restart.

Storage policies​

  • Maximum upload size for one or multiple files: 10 MB
  • File expiration time/time-to-live (TTL) policy: With Self-Managed, users may define their own lifecycle policies. A custom expiration date can be specified via the document upload API.