Cross-cluster search (CCS) allows you to configure multiple remote deployments, and enable federated search queries across all of the configured deployments.
Cluster settings are automatically maintained and updated when cluster topologies change. For example, all connected clusters are updated when:
- A cluster is deleted
- A node is added or removed from a cluster
Once your remotes are configured, you can run CCS queries from Elasticsearch.
Cross-cluster search is not supported for AWS Marketplace accounts.
To enable CCS, you must meet the following criteria:
- All clusters must be in the same same Elasticsearch Service environment, region, and owned by the same user.
All deployments must be version 5.6.x or later.
- Review the Elasticsearch version compatibility table.
- System deployments are not compatible with CCS.
- To access the RESTful API for Elasticsearch Service, you must use your Elasticsearch Service credentials.
The CCS deployment acts as a hub that manages all of the remote deployment connections.
- Log into the Elasticsearch Service Console.
- Click Create deployment.
- Select the Cross Cluster Search template.
Decide when to add the remote connections:
- If you know the deployments that you want to include, click Customize deployment to define the remotes while creating the deployment.
- After the deployment is spun up, you can add remotes from the deployment overview page.
- Click Add deployment.
Select a target deployment from the Deployment name drop-down list.
Only the compatible deployments appear on this list.
- Optional: Update the generated alias to something meaningful to you.
- Save your changes.
- Verify the configuration by running CCS queries from Elasticsearch.
- As needed, from the Elasticsearch API or Kibana, update the Elasticsearch cluster security and user access roles to allow them to access the remote deployments.
The target deployment overview page shows which CCS deployments can search the target.