cleanup

Author: shainaraskas

deploy-manage/remote-clusters.md

@@ -1,24 +1,15 @@
 ---
 applies_to:
-  stack: ga
   deployment:
     ece: ga
     eck: ga
     ess: ga
     self: ga
-  serverless: unavailable
+    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:

deploy-manage/remote-clusters/ec-enable-ccs.md

@@ -27,7 +27,7 @@ To use CCS or CCR, your deployments must meet the following criteria:
   :::{include} _snippets/remote-cluster-certificate-compatibility.md
   :::
 
-* If your deployment was created before February 2021, the Remote clusters page in {{kib}} must be enabled manually from the **Security** page of your deployment, by selecting **Enable CCR** under **Trust management**.
+* If your deployment was created before February 2021, the **Remote clusters** page in {{kib}} must be enabled manually from the **Security** page of your deployment, by selecting **Enable CCR** under **Trust management**.
 
 ## Set up remote clusters with {{ech}}
 
@@ -45,8 +45,8 @@ The steps, information, and authentication method required to configure CCS and
 
     * [From another deployment of your {{ecloud}} organization](ec-remote-cluster-same-ess.md)
     * [From a deployment of another {{ecloud}} organization](ec-remote-cluster-other-ess.md)
-    * [From an ECE deployment](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-enable-ccs.html)
-    * [From a self-managed cluster](https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters.html)
+    * [From an ECE deployment](ece-remote-cluster-ece-ess.md)
+    * [From a self-managed cluster](remote-clusters-self-managed.md)
     * [From an ECK environment](ec-enable-ccs-for-eck.md)
 
 

deploy-manage/remote-clusters/ec-migrate-ccs.md

@@ -4,6 +4,7 @@ applies_to:
     ess: ga
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-migrate-ccs.html
+navigation_title: "Migrate the CCS deployment template"
 ---
 
 # Migrate the cross-cluster search deployment template [ec-migrate-ccs]

deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md

@@ -33,20 +33,20 @@ On the local cluster side, not every local user needs to access every piece of d
 If you run into any issues, refer to [Troubleshooting](remote-clusters-troubleshooting.md).
 
 
-#### Prerequisites and limitations [ec_prerequisites_and_limitations]
+### Prerequisites and limitations [ec_prerequisites_and_limitations]
 
 * The local and remote deployments must be on {{stack}} 8.14 or later.
 * API key authentication can’t be used in combination with traffic filters.
 * Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
 
 
-#### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment]
+### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment]
 
 * On the deployment you will use as remote, use the [{{es}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) or [{{kib}}](../api-keys/elasticsearch-api-keys.md) to create a cross-cluster API key. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 * Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next step.
 
 
-#### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment]
+### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment]
 
 The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
 
@@ -76,7 +76,7 @@ If you later need to update the remote connection with different permissions, yo
 ::::::
 
 ::::::{tab-item} TLS certificate (deprecated)
-#### Set the default trust with other clusters in the same {{ecloud}} organization [ec_set_the_default_trust_with_other_clusters_in_the_same_elasticsearch_service_organization]
+### Set the default trust with other clusters in the same {{ecloud}} organization [ec_set_the_default_trust_with_other_clusters_in_the_same_elasticsearch_service_organization]
 
 By default, any deployment that you create trusts all other deployments in the same organization. You can change this behavior in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) under **Features** > **Trust**, so that when a new deployment is created it does not automatically trust any other deployment. You can choose one of the following options:
 
@@ -96,7 +96,7 @@ By default, any deployment that you create trusts all other deployments in the s
 
 
 
-#### Specify the deployments trusted to be used as remote clusters [ec_specify_the_deployments_trusted_to_be_used_as_remote_clusters]
+### Specify the deployments trusted to be used as remote clusters [ec_specify_the_deployments_trusted_to_be_used_as_remote_clusters]
 
 If your organization’s deployments already trust each other by default, you can skip this section. If that’s not the case, follow these steps to configure which are the specific deployments that should be trusted.
 

deploy-manage/remote-clusters/ece-migrate-ccs.md

@@ -4,6 +4,7 @@ applies_to:
     ece: ga
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-ccs.html
+navigation_title: "Migrate the CCS deployment template"
 ---
 
 # Migrate the cross-cluster search deployment template [ece-migrate-ccs]