From 305369f17bd5d82e522948dd111f42b1cb50a68a Mon Sep 17 00:00:00 2001 From: kosabogi Date: Mon, 3 Mar 2025 12:54:15 +0100 Subject: [PATCH 1/4] Adds Access isolation overview page --- .../access-isolation-for-found-snapshots-repository.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md index 3aaa73d650..c5f7e80c92 100644 --- a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md @@ -6,10 +6,18 @@ applies_to: # Access isolation for the found-snapshots repository [ec-snapshot-repository-migration] +In {{ech}}, [snapshots](/deploy-manage/tools/snapshot-and-restore) are stored in a repository. By default, deployments in the same region may have access to each other’s snapshots through the `found-snapshots` repository. + +To enhance security, access isolation ensures that each deployment can only access its own snapshots. This prevents accidental or unauthorized access to backups from other deployments within the same organization. + ::::{note} The guides in this section are only relevant for some deployments. Any newly created deployment will have access isolation set up by default. If a deployment’s repository can be updated, a notification will show up in the deployments menu under **Elasticsearch** > **Snapshots**. :::: +The process for enabling access isolation depends on your cloud provider: + +* [Azure deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp) +* [AWS & GCP deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure) From 3c4feb8ce988f0c0641bff74073dd0f6d91e51e3 Mon Sep 17 00:00:00 2001 From: kosabogi Date: Mon, 3 Mar 2025 13:01:49 +0100 Subject: [PATCH 2/4] Fixing links --- .../access-isolation-for-found-snapshots-repository.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md index c5f7e80c92..2145bd0222 100644 --- a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md @@ -6,7 +6,7 @@ applies_to: # Access isolation for the found-snapshots repository [ec-snapshot-repository-migration] -In {{ech}}, [snapshots](/deploy-manage/tools/snapshot-and-restore) are stored in a repository. By default, deployments in the same region may have access to each other’s snapshots through the `found-snapshots` repository. +In {{ech}}, [snapshots](/deploy-manage/tools/snapshot-and-restore.md) are stored in a repository. By default, deployments in the same region may have access to each other’s snapshots through the `found-snapshots` repository. To enhance security, access isolation ensures that each deployment can only access its own snapshots. This prevents accidental or unauthorized access to backups from other deployments within the same organization. @@ -16,8 +16,8 @@ The guides in this section are only relevant for some deployments. Any newly cre The process for enabling access isolation depends on your cloud provider: -* [Azure deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp) -* [AWS & GCP deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure) +* [Azure deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md) +* [AWS & GCP deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md) From 3aaec551cce5017a4e4892a5a2b5b343a59c5014 Mon Sep 17 00:00:00 2001 From: kosabogi <105062005+kosabogi@users.noreply.github.com> Date: Mon, 3 Mar 2025 14:38:06 +0100 Subject: [PATCH 3/4] Update deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com> --- .../access-isolation-for-found-snapshots-repository.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md index 2145bd0222..19a07fe209 100644 --- a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md @@ -10,9 +10,6 @@ In {{ech}}, [snapshots](/deploy-manage/tools/snapshot-and-restore.md) are stored To enhance security, access isolation ensures that each deployment can only access its own snapshots. This prevents accidental or unauthorized access to backups from other deployments within the same organization. -::::{note} -The guides in this section are only relevant for some deployments. Any newly created deployment will have access isolation set up by default. If a deployment’s repository can be updated, a notification will show up in the deployments menu under **Elasticsearch** > **Snapshots**. -:::: The process for enabling access isolation depends on your cloud provider: From f23c07810b40df66212b06ba5cec3cf352c54d41 Mon Sep 17 00:00:00 2001 From: kosabogi Date: Mon, 3 Mar 2025 14:59:18 +0100 Subject: [PATCH 4/4] Update access isolation page --- .../access-isolation-for-found-snapshots-repository.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md index 19a07fe209..b431ede6ef 100644 --- a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md @@ -6,10 +6,11 @@ applies_to: # Access isolation for the found-snapshots repository [ec-snapshot-repository-migration] -In {{ech}}, [snapshots](/deploy-manage/tools/snapshot-and-restore.md) are stored in a repository. By default, deployments in the same region may have access to each other’s snapshots through the `found-snapshots` repository. +In {{ech}}, access isolation ensures that each deployment can access only its own snapshots, preventing accidental or unauthorized access to backups from other deployments within the same organization. -To enhance security, access isolation ensures that each deployment can only access its own snapshots. This prevents accidental or unauthorized access to backups from other deployments within the same organization. +Any newly created deployment has snapshot isolation set up by default. The guides in these section apply only to older deployments created before this default was implemented, where deployments within the same region may still have access to each other’s snapshots. +If a deployment can access the snapshots of other deployments, a notification will appear in the deployments menu under **Elasticsearch > Snapshots**, prompting you to set up access isolation. The process for enabling access isolation depends on your cloud provider: