Loading

Remote clusters on Elastic Cloud on Kubernetes

ECK

The remote clusters feature in Elasticsearch enables you to establish uni-directional connections to a remote cluster. This functionality is used in cross-cluster replication (CCR) and cross-cluster search (CCS).

Note about terminology

In the case of remote clusters, the Elasticsearch cluster or deployment initiating the connection and requests is often referred to as the local cluster, while the Elasticsearch cluster or deployment receiving the requests is referred to as the remote cluster.

When using remote cluster connections with ECK, the setup process varies depending on how both the local and remote clusters are deployed:

  • When both clusters are managed by the same operator, ECK can automate certificate and API-key management, connection configuration, and reconciliation.
  • When external clusters are involved, ECK provides limited automation, and additional manual configuration is required on both the local and remote clusters.

To use CCS or CCR, your Elasticsearch clusters must meet the following criteria:

  • The local and remote clusters must run on compatible versions of Elasticsearch. Review the version compatibility table.

  • Network connectivity between the clusters. Review the connection modes and the security models to understand the connectivity requirements for your specific setup. Remote cluster connections can operate through Kubernetes services, load balancers, reverse proxies, or other intermediaries, as long as the local cluster can reach the remote cluster’s endpoint.

  • The remote clusters feature on ECK requires a valid Enterprise license or Enterprise trial license. Check the license documentation for more details about managing licenses.

Use one of the following guides depending on how the local and remote clusters are deployed.

Connect from ECK-managed clusters:

Connect to ECK-managed clusters from external clusters: