Loading

Remote clusters on Elastic Cloud Enterprise

ECE

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

  • Another deployment of your ECE installation
  • A deployment running on a different ECE installation
  • An Elastic Cloud Hosted deployment
  • A deployment running on 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 filters and the implications for your deployments.

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

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

  • Proxies must answer TCP requests on the port 9400. Check the prerequisites for the ports that must permit outbound or inbound traffic.

  • Load balancers must pass-through TCP requests on port 9400. Check the configuration details.

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

Note

System deployments cannot be used as remote clusters or have remote clusters.

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.