Loading

Remote clusters on Elastic Cloud Hosted

ECH

You can configure an Elastic Cloud Hosted deployment to either connect to remote clusters or accept connections from:

  • Another Elastic Cloud Hosted deployment of your Elastic Cloud organization, across any region or cloud provider (AWS, GCP, Azure…)
  • An Elastic Cloud Hosted deployment of another Elastic Cloud organization
  • A deployment in an Elastic Cloud Enterprise installation
  • A deployment in an Elastic Cloud on Kubernetes installation
  • A self-managed installation.
Note

Refer to Remote clusters and network security for details on how remote clusters interact with network security policies and the implications for your deployments.

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

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

  • If your deployment was created before February 2021, the Remote clusters page in Kibana must be enabled manually from the Security page of your deployment, by selecting Enable CCR under Trust management.

The steps, information, and authentication method required to configure CCS and CCR can vary depending on where the clusters you want to use as remote are hosted.

If you have network security policies applied to the remote cluster, you might need to take extra steps on the remote side to allow traffic from the local cluster. Some remote cluster configurations have limited compatibility with network security. To learn more, refer to Remote clusters and network security.