resolving all pending issues

eedugon · eedugon · commit 618845ce703a · 2025-10-16T09:47:00.000+02:00
diff --git a/deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet-self.md b/deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet-self.md
@@ -5,6 +5,7 @@ This snippet is in use in the following locations:
 -->
 To configure a self-managed cluster as a remote cluster, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). Configure the following fields:
 
+* `Remote cluster alias`: When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI as **Remote cluster name**.
 * `mode`: `proxy`
 * `proxy_address`: Enter the endpoint of the remote self-managed cluster, including the hostname, FQDN, or IP address, and the port. Both IPv4 and IPv6 addresses are supported.
 
@@ -35,8 +36,4 @@ PUT /_cluster/settings
 }
 ```
 
-::::{note}
-When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI.
-::::
-
 For a full list of available client connection settings in proxy mode, refer to [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).
diff --git a/deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet.md b/deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet.md
@@ -11,6 +11,7 @@ It requires remote_type substitution to be defined
 -->
 To configure a deployment as a remote cluster, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). Configure the following fields:
 
+* `Remote cluster alias`: When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI as **Remote cluster name**.
 * `mode`: `proxy`
 * `proxy_address`: This value can be found on the **Security** page of the {{remote_type}} you want to use as a remote. Copy the **Proxy address** from the **Remote cluster parameters** section. Also, using the API, this value can be obtained from the {{es}} resource info, concatenating the field `metadata.endpoint` and port `9400` using a semicolon.
 
@@ -39,6 +40,4 @@ PUT /_cluster/settings
 }
 ```
 
-::::{note}
-When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI.
-::::
+For a full list of available client connection settings in proxy mode, refer to [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
@@ -210,7 +210,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 If you’re having issues establishing the connection and the remote cluster is part of an {{ece}} environment with a private certificate, make sure that the proxy address and server name match with the the certificate information. For more information, refer to [Administering endpoints in {{ece}}](/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md).
 ::::
 
-### Using the {{es}} API [ec_using_the_elasticsearch_api_3]
+### Using the {{es}} RESTful API [ec_using_the_elasticsearch_api_3]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
@@ -145,7 +145,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 :::
 
 
-### Using the {{es}} API [ec_using_the_elasticsearch_api_2]
+### Using the {{es}} RESTful API [ec_using_the_elasticsearch_api_2]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
@@ -165,20 +165,20 @@ You can now connect remotely to the trusted clusters.
 
 ## Connect to the remote cluster [ec_connect_to_the_remote_cluster]
 
-On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
+On the local cluster, add the remote cluster using {{kib}}, the {{es}} API, or the {{ecloud}} API.
 
 
 ### Using {{kib}} [ec_using_kibana]
 
 :::{include} _snippets/rcs-kibana-api-snippet.md
 :::
 
-### Using the {{es}} API [ec_using_the_elasticsearch_api]
+### Using the {{es}} RESTful API [ec_using_the_elasticsearch_api]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
 
-### Using the {{ecloud}} API [ec_using_the_elasticsearch_service_restful_api]
+### Using the {{ecloud}} RESTful API [ec_using_the_elasticsearch_service_restful_api]
 ```{applies_to}
 deployment:
   ess: deprecated
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
@@ -224,7 +224,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 :::{include} _snippets/rcs-kibana-api-snippet-self.md
 :::
 
-### Using the {{es}} API [ec_using_the_elasticsearch_api_4]
+### Using the {{es}} RESTful API [ec_using_the_elasticsearch_api_4]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet-self.md
 :::
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md
@@ -143,7 +143,6 @@ You can now connect remotely to the trusted clusters.
 
 On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
-% ECE locals only
 ::::{note}
 This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#proxy-mode) and requires the ECE allocators to be able to connect to the remote address endpoint.
 ::::
@@ -154,7 +153,7 @@ This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remot
 :::{include} _snippets/rcs-kibana-api-snippet.md
 :::
 
-### Using the {{es}} API [ece_using_the_elasticsearch_api_3]
+### Using the {{es}} RESTful API [ece_using_the_elasticsearch_api_3]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md
@@ -215,7 +215,6 @@ You can now connect remotely to the trusted clusters.
 
 On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
-% ECE locals only
 ::::{note}
 This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#proxy-mode) and requires the ECE allocators to be able to connect to the remote address endpoint.
 ::::
@@ -230,7 +229,7 @@ If you’re having issues establishing the connection and the remote cluster is
 ::::
 
 
-### Using the {{es}} API [ece_using_the_elasticsearch_api_2]
+### Using the {{es}} RESTful API [ece_using_the_elasticsearch_api_2]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md
@@ -169,9 +169,8 @@ You can now connect remotely to the trusted clusters.
 
 ## Connect to the remote cluster [ece_connect_to_the_remote_cluster]
 
-On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
+On the local cluster, add the remote cluster using {{kib}}, the {{es}} API, or the ECE API.
 
-% ECE locals only
 ::::{note}
 This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#proxy-mode) and requires the ECE allocators to be able to connect to the remote address endpoint.
 ::::
@@ -185,12 +184,12 @@ This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remot
 If you’re having issues establishing the connection and the remote cluster is part of an {{ece}} environment with a private certificate, make sure that the proxy address and server name match with the the certificate information. For more information, refer to [Administering endpoints in {{ece}}](/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md).
 ::::
 
-### Using the {{es}} API [ece_using_the_elasticsearch_api]
+### Using the {{es}} RESTful API [ece_using_the_elasticsearch_api]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
 
-### Using the {{ece}} API [ece_using_the_elastic_cloud_enterprise_restful_api]
+### Using the {{ece}} RESTful API [ece_using_the_elastic_cloud_enterprise_restful_api]
 ```{applies_to}
 deployment:
   ece: deprecated
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md
@@ -217,7 +217,6 @@ You can now connect remotely to the trusted clusters.
 
 On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
-% ECE locals only
 ::::{note}
 This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#proxy-mode) and requires the ECE allocators to be able to connect to the remote address endpoint.
 ::::
@@ -227,7 +226,7 @@ This configuration of remote clusters uses the [Proxy mode](/deploy-manage/remot
 :::{include} _snippets/rcs-kibana-api-snippet-self.md
 :::
 
-### Using the {{es}} API [ece_using_the_elasticsearch_api_4]
+### Using the {{es}} RESTful API [ece_using_the_elasticsearch_api_4]
 
 :::{include} _snippets/rcs-elasticsearch-api-snippet-self.md
 :::
diff --git a/deploy-manage/remote-clusters/remote-clusters-api-key.md b/deploy-manage/remote-clusters/remote-clusters-api-key.md
@@ -162,7 +162,7 @@ To add a remote cluster from Stack Management in {{kib}}:
 
     Starting with {{kib}} 9.2, you can also specify IPv6 addresses.
 
-### Using the {{es}} API
+### Using the {{es}} RESTful API
 
 Alternatively, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to add a remote cluster. You can also use this API to dynamically configure remote clusters for *every* node in the local cluster. To configure remote clusters on individual nodes in the local cluster, define static settings in [`elasticsearch.yml`](/deploy-manage/stack-settings.md) for each node.
 
diff --git a/deploy-manage/remote-clusters/remote-clusters-cert.md b/deploy-manage/remote-clusters/remote-clusters-cert.md
@@ -72,7 +72,7 @@ To add a remote cluster from Stack Management in {{kib}}:
 
     Starting with {{kib}} 9.2, you can also specify IPv6 addresses.
 
-### Using the {{es}} API
+### Using the {{es}} RESTful API
 
 Alternatively, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to add a remote cluster. You can also use this API to dynamically configure remote clusters for *every* node in the local cluster. To configure remote clusters on individual nodes in the local cluster, define static settings in [`elasticsearch.yml`](/deploy-manage/stack-settings.md) for each node.
 
