Version 7.17.3, 8.1.3 & 8.3.1

Fully automate all end-to-end operations for deploying and managing Elasticsearch. ClusterControl’s automation enables you to focus on your ELK stack without the burden of manual configuration or admin tasks.

Tech highlights


  • Elasticsearch
  • Operating system provided repository
  • Custom repository binaries

Replication types

  • In-sync replica copies

Top features

  • Secure communication
  • Scalability
  • Snapshot backups

Elasticsearch + ClusterControl Scale at your own speed

Deploy a single instance Elasticsearch, add data nodes, and scale out your architecture as needed. Create a replica and grow your shards with the click of a button.

Try ClusterControl with Elasticsearch for yourself!

Features list

OSS Licensecheck
Enterprise License
Severalnines Supportcheck
Storage Engines
Time series
Backup & Restorecheck
— Fullcheck
— Incremental
— Partial
— Restore: PITR
— Clone / Duplicate nodecheck
— Local storagecheck
— Cloud storagecheck
— Encryption
— Compression
Cluster creationcheck
— Asynchronous Replication
— Synchronous Replicationcheck
— Add node / decommissioncheck
SSL/TLS Connectivitycheck
Load Balancer availability
Infrastructure manageabilitycheck
Security summary
— User console accesscheck
— Key Managementcheck
— LDAP integrationcheck
— Audit logcheck
Performance analysis
— Query monitoringcheck
— Operations monitoringcheck
— Custom metrics/thresholdscheck
— Replication lag
Configuration Managementcheck
Database-specific dashboardcheck
Alarms & Error reportingcheck

Top rated Docs

Create a Database Cluster docs

Backups docs

Nodes docs

Top rated Blogs

What is Elasticsearch and why use it?

A true alternative to Elastic Cloud for Elasticsearch ops automation

Managing Multiple Database Technologies with ClusterControl

I use Kibana with my Elasticsearch deployment for data manipulation. Does ClusterControl include that functionality too?

With ClusterControl, we focus on what we know best which is automating database provisioning and maintenance. The rest we let you decide so you can keep using Kibana as always.

Should I switch from using my PostgreSQL as a primary database deployment with ClusterControl to using Elasticsearch, as I have terabytes of data I need to go through?

In general, just keep using PostgreSQL as you do now and have a look at the available integrations for connecting with Elasticsearch, as once you’ve automated deployment with ClusterControl, the rest is just connectivity to your desire.

Given the amount of data, I don’t normally take backups for Elasticsearch. What do you recommend?

For DR and as part of a good B’n’R strategy, we highly recommend not only the use of a cluster for HA but using the Elasticsearch snapshot capability that allows you to store the backups locally or on AWS S3.

6 easy steps to get started with ClusterControl