Configure Elasticsearch and OpenSearch for Orchestration Cluster in Helm

Use this page as the navigation hub for Elasticsearch and OpenSearch configuration for the Orchestration Cluster in Helm deployments.

This page applies to the Orchestration Cluster only. If you also deploy Optimize, use the dedicated Optimize database configuration pages for Optimize-specific settings.

Configure secondary storage backends

Use the following pages based on your backend:

• Use external Elasticsearch with Helm
• Use Amazon OpenSearch Service with the Helm chart

Shared Elasticsearch and OpenSearch tasks

Use the following pages when you need settings that can apply to both the Orchestration Cluster and Optimize:

• Configure custom HTTP headers for database clients
• Configure Elasticsearch and OpenSearch index prefixes

Troubleshooting

• All shards failed errors

Related concepts

• Secondary storage overview
• Elasticsearch/OpenSearchElasticsearch/OpenSearchElasticsearch and OpenSearch are search and analytics engines commonly used as document-store secondary storage backends for indexing and querying exported runtime data. They are populated with process orchestration data and consumed by components such as Operate, Tasklist, and Optimize.