Cross-cluster search (CCS) allows you to configure multiple remote clusters across different locations and to enable federated search queries across all of the configured remote clusters.
Cross-cluster replication (CCR) allows you to replicate indices across multiple remote clusters regardless of where they’re located. This provides tremendous benefit in scenarios of disaster recovery or data locality.
These remote clusters could be:
- Another Elasticsearch cluster of your Elastic Cloud organization across any region or cloud provider (AWS, GCP, Azure…)
- An Elasticsearch cluster of another organization
- An Elasticsearch cluster in an Elastic Cloud Enterprise installation
- Any other self-managed Elasticsearch cluster
These steps describe how to configure remote clusters. Once that’s done, you’ll be able to run CCS queries from Elasticsearch or set up CCR.
You no longer need to use the dedicated cross-cluster search template to search across clusters. You can now use any template to configure remote clusters and search across them when using stack version 6.7 or above. We’ve deprecated the cross-cluster search template. Existing deployments created using this template are not affected by this change, but they need to migrate to another template before upgrading to the next 8.0 major version.
Before you beginedit
To use CCS or CCR, your deployments must meet the following criteria:
- To use CCS, local and remote clusters must be version 6.7.x or higher.
- To use CCR, local and remote clusters must be at version 6.8.9 or higher (in the 6.x branch), or 7.7.1 or higher (in the 7.x branch).
- Local and remote clusters must be in compatible versions. Review the Elasticsearch version compatibility table.
- The local and remote cluster must trust each other.
Intro to Kibana
ELK for Logs & Metrics