From 1881d416d2ef5bcf69868a7867f475628a5454bf 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, 29 Oct 2025 11:11:44 +0100 Subject: [PATCH] extra snippets added --- .../_snippets/apikeys-local-config-intro.md | 1 + .../_snippets/apikeys-prerequisites-limitations.md | 2 ++ deploy-manage/remote-clusters/ec-remote-cluster-ece.md | 7 ++++--- .../remote-clusters/ec-remote-cluster-other-ess.md | 7 ++++--- .../remote-clusters/ec-remote-cluster-same-ess.md | 7 ++++--- .../remote-clusters/ec-remote-cluster-self-managed.md | 7 ++++--- .../remote-clusters/ece-remote-cluster-ece-ess.md | 6 ++++-- .../remote-clusters/ece-remote-cluster-other-ece.md | 6 ++++-- .../remote-clusters/ece-remote-cluster-same-ece.md | 6 ++++-- .../remote-clusters/ece-remote-cluster-self-managed.md | 6 ++++-- 10 files changed, 35 insertions(+), 20 deletions(-) create mode 100644 deploy-manage/remote-clusters/_snippets/apikeys-local-config-intro.md create mode 100644 deploy-manage/remote-clusters/_snippets/apikeys-prerequisites-limitations.md diff --git a/deploy-manage/remote-clusters/_snippets/apikeys-local-config-intro.md b/deploy-manage/remote-clusters/_snippets/apikeys-local-config-intro.md new file mode 100644 index 0000000000..5611e1ee12 --- /dev/null +++ b/deploy-manage/remote-clusters/_snippets/apikeys-local-config-intro.md @@ -0,0 +1 @@ +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. diff --git a/deploy-manage/remote-clusters/_snippets/apikeys-prerequisites-limitations.md b/deploy-manage/remote-clusters/_snippets/apikeys-prerequisites-limitations.md new file mode 100644 index 0000000000..1619df67e1 --- /dev/null +++ b/deploy-manage/remote-clusters/_snippets/apikeys-prerequisites-limitations.md @@ -0,0 +1,2 @@ +* The local and remote deployments must be on {{stack}} 8.14 or later. +* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other. diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md index c5ac2c8e02..476ce601e9 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md @@ -34,8 +34,8 @@ If network security filters are applied to the remote cluster on ECE, the remote ### Prerequisites and limitations [ec_prerequisites_and_limitations_3] -* The local and remote deployments must be on {{stack}} 8.14 or later. -* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_3] @@ -46,7 +46,8 @@ If network security filters are applied to the remote cluster on ECE, the remote ### Configure the local deployment [ec_configure_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. +:::{include} _snippets/apikeys-local-config-intro.md +::: The steps to follow depend on whether the Certificate Authority (CA) of the remote ECE environment’s proxy or load balancing infrastructure is public or private. diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md index 95d3ac28e4..0c815ff348 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md @@ -34,8 +34,8 @@ If network security policies are applied to the remote cluster, the remote clust ### Prerequisites and limitations [ec_prerequisites_and_limitations_2] -* The local and remote deployments must be on {{stack}} 8.14 or later. -* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_2] @@ -45,7 +45,8 @@ If network security policies are applied to the remote cluster, the remote clust ### 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_2] -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. +:::{include} _snippets/apikeys-local-config-intro.md +::: :::{include} _snippets/apikeys-local-ech-remote-public.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 index ae39a1d29b..d9c838abca 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -34,8 +34,8 @@ If network security policies are applied to the remote cluster, the remote clust ### Prerequisites and limitations [ec_prerequisites_and_limitations] -* The local and remote deployments must be on {{stack}} 8.14 or later. -* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment] @@ -45,7 +45,8 @@ If network security policies are applied to the remote cluster, the remote clust ### Add the cross-cluster API key to the local deployment [ec_add_the_cross_cluster_api_key_to_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. +:::{include} _snippets/apikeys-local-config-intro.md +::: :::{include} _snippets/apikeys-local-ech-remote-public.md ::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md index f18784711a..41a2e5659a 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md @@ -29,8 +29,8 @@ This section explains how to configure a deployment to connect remotely to self- ### Prerequisites and limitations [ec_prerequisites_and_limitations_4] -* The local and remote deployments must be on {{stack}} 8.14 or later. -* Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_4] @@ -40,7 +40,8 @@ This section explains how to configure a deployment to connect remotely to self- ### Configure the local deployment [ec_configure_the_local_deployment_2] -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. +:::{include} _snippets/apikeys-local-config-intro.md +::: The steps to follow depend on whether the Certificate Authority (CA) of the remote environment’s {{es}} HTTPS server, proxy or, load balancing infrastructure is public or private. diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md index 9596344756..3ff8e83f6a 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -35,7 +35,8 @@ If network security filters are applied to the remote cluster on {{ecloud}}, the ### Prerequisites and limitations [ece_prerequisites_and_limitations_3] -* The local and remote deployments must be on {{stack}} 8.14 or later. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_3] @@ -45,7 +46,8 @@ If network security filters are applied to the remote cluster on {{ecloud}}, the ### Add the cross-cluster API key to the keystore of the local deployment [ece_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment_2] -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. +:::{include} _snippets/apikeys-local-config-intro.md +::: :::{include} _snippets/apikeys-local-ece-remote-public.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 index 9567e4ecc0..6acac7e01c 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -34,7 +34,8 @@ If network security filters are applied to the remote cluster on ECE, the remote ### Prerequisites and limitations [ece_prerequisites_and_limitations_2] -* The local and remote deployments must be on {{stack}} 8.14 or later. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_2] @@ -43,7 +44,8 @@ If network security filters are applied to the remote cluster on ECE, the remote ### Configure the local deployment [ece_configure_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. +:::{include} _snippets/apikeys-local-config-intro.md +::: The steps to follow depend on whether the Certificate Authority (CA) of the remote ECE environment’s proxy or load balancing infrastructure is public or private. diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md index 0ff3d7350c..4b3e01c7b9 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -34,7 +34,8 @@ If network security filters are applied to the remote cluster, the remote cluste ### Prerequisites and limitations [ece_prerequisites_and_limitations] -* The local and remote deployments must be on {{stack}} 8.14 or later. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment] @@ -44,7 +45,8 @@ If network security filters are applied to the remote cluster, the remote cluste ### Add the cross-cluster API key to the keystore of the local deployment [ece_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. +:::{include} _snippets/apikeys-local-config-intro.md +::: :::{include} _snippets/apikeys-local-ece-remote-public.md ::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md index 40da4766a5..fba4ce00fc 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -30,7 +30,8 @@ This section explains how to configure a deployment to connect remotely to self- ### Prerequisites and limitations [ece_prerequisites_and_limitations_4] -* The local and remote deployments must be on {{stack}} 8.14 or later. +:::{include} _snippets/apikeys-prerequisites-limitations.md +::: ### Create a cross-cluster API key on the remote deployment [ece_create_a_cross_cluster_api_key_on_the_remote_deployment_4] @@ -40,7 +41,8 @@ This section explains how to configure a deployment to connect remotely to self- ### Configure the local deployment [ece_configure_the_local_deployment_2] -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. +:::{include} _snippets/apikeys-local-config-intro.md +::: The steps to follow depend on whether the Certificate Authority (CA) of the remote environment’s {{es}} HTTPS server, proxy or, load balancing infrastructure is public or private.