[D&M] Remote clusters cleanup #443
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,49 @@ | ||
| --- | ||
| applies_to: | ||
| stack: ga | ||
| deployment: | ||
shainaraskas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ece: ga | ||
| eck: ga | ||
| ess: ga | ||
| self: ga | ||
| serverless: unavailable | ||
| --- | ||
|
|
||
| # Remote clusters [remote-clusters] | ||
|
|
||
| % What needs to be done: Write from scratch | ||
|
|
||
| % GitHub issue: https://github.com/elastic/docs-projects/issues/345 | ||
|
|
||
| % Scope notes: "Landing page for cross cluster comms, used by CCS and CCR. | ||
| % We will cover here the raw configuration at Elasticsearch level and the docs to enable remote clusters in ESS / ECE / ECK. | ||
| % We can include links to the use cases of remote clusters, such as CCR and CCS." | ||
|
|
||
| By setting up **remote clusters**, you can connect an {{es}} cluster to other {{es}} clusters. Remote clusters can be located in different data centers, geographic regions, and run on a different type of environment: {{ech}}, {{ece}}, {{eck}}, or self-managed. | ||
|
|
||
| Remote clusters are especially useful in two cases: | ||
|
|
||
| - **Cross-cluster replication** | ||
| With [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md), or CCR, you ingest data to an index on a remote cluster. This leader index is replicated to one or more read-only follower indices on your local cluster. Creating a multi-cluster architecture with cross-cluster replication enables you to configure disaster recovery, bring data closer to your users, or establish a centralized reporting cluster to process reports locally. | ||
|
|
||
| - **Cross-cluster search** | ||
| [Cross-cluster search](/solutions/search/cross-cluster-search.md), or CCS, enables you to run a search request against one or more remote clusters. This capability provides each region with a global view of all clusters, allowing you to send a search request from a local cluster and return results from all connected remote clusters. For full {{ccs}} capabilities, the local and remote cluster must be on the same [subscription level](https://www.elastic.co/subscriptions). | ||
|
|
||
| ::::{note} about terminology | ||
| In the case of remote clusters, the {{es}} cluster or deployment initiating the connection and requests is often referred to as the **local cluster**, while the {{es}} cluster or deployment receiving the requests is referred to as the **remote cluster**. | ||
| :::: | ||
|
|
||
| ## Setup | ||
|
|
||
| Depending on the environment the local and remote clusters are deployed on and the security model you wish to use, the exact details needed to add a remote cluster vary but generally follow the same path: | ||
|
|
||
| 1. **Configure trust between clusters.** In the settings of the local deployment or cluster, configure the trust security model that your remote connections will use to access the remote cluster. This step involves specifying API keys or certificates retrieved from the remote clusters. | ||
|
|
||
| 2. **Establish the connection.** In {{kib}} on the local cluster, finalize the connection by specifying each remote cluster's details. | ||
|
|
||
| Find the instructions with details on the supported security models and available connection modes for your specific scenario: | ||
|
|
||
| - [Remote clusters with {{ech}}](remote-clusters/ec-enable-ccs.md) | ||
| - [Remote clusters with {{ece}}](remote-clusters/ece-enable-ccs.md) | ||
| - [Remote clusters with {{eck}}](remote-clusters/eck-remote-clusters.md) | ||
| - [Remote clusters with self-managed installations](remote-clusters/remote-clusters-self-managed.md) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| :::::{dropdown} Version compatibility table | ||
|
|
||
| * Any node can communicate with another node on the same major version. For example, 9.0 can talk to any 9.x node. | ||
| * Version compatibility is symmetric, meaning that if 7.16 can communicate with 8.0, 8.0 can also communicate with 7.16. The following table depicts version compatibility between local and remote nodes. | ||
|
|
||
| | | | | ||
| | --- | --- | | ||
| | | Local cluster | | ||
| | Remote cluster | 5.0–5.5 | 5.6 | 6.0–6.6 | 6.7 | 6.8 | 7.0 | 7.1–7.16 | 7.17 | 8.0–9.0 | | ||
| | 5.0–5.5 |  |  |  |  |  |  |  |  |  | | ||
| | 5.6 |  |  |  |  |  |  |  |  |  | | ||
| | 6.0–6.6 |  |  |  |  |  |  |  |  |  | | ||
| | 6.7 |  |  |  |  |  |  |  |  |  | | ||
| | 6.8 |  |  |  |  |  |  |  |  |  | | ||
| | 7.0 |  |  |  |  |  |  |  |  |  | | ||
| | 7.1–7.16 |  |  |  |  |  |  |  |  |  | | ||
| | 7.17 |  |  |  |  |  |  |  |  |  | | ||
| | 8.0–9.0 |  |  |  |  |  |  |  |  |  | | ||
|
|
||
|
|
||
| ::::{important} | ||
| Elastic only supports {{ccs}} on a subset of these configurations. See [Supported {{ccs}} configurations](../../../solutions/search/cross-cluster-search.md#ccs-supported-configurations). | ||
| :::: | ||
|
|
||
| ::::: | ||
|
|
||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a perfect page????