From 656e4e6334643c88b604b4f62d23374987702de3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?=
<25320357+eedugon@users.noreply.github.com>
Date: Wed, 1 Oct 2025 14:10:40 +0200
Subject: [PATCH] fixed incorrect reference to ech
---
deploy-manage/remote-clusters/ec-remote-cluster-ece.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
index 5caf2334a8..8241b4544c 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
@@ -204,13 +204,13 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
* **Name**: This *cluster alias* is a unique identifier that represents the connection to the remote cluster and is used to distinguish local and remote indices.
When using API key authentication, this alias must match the **Remote cluster name** you configured when adding the API key in the Cloud UI.
- * **Proxy address**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote.
+ * **Proxy address**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote.
::::{tip}
If you’re using API keys as security model, change the port into `9443`.
::::
- * **Server name**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote.
+ * **Server name**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote.
::::{note}
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).