Skip to content

Adds conceptual description to the Access isolation overview page #634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Mar 3, 2025
Merged

Adds conceptual description to the Access isolation overview page #634

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
305369f
Adds Access isolation overview page
kosabogi Mar 3, 2025
3c4feb8
Fixing links
kosabogi Mar 3, 2025
3aaec55
Update deploy-manage/tools/snapshot-and-restore/access-isolation-for-…
kosabogi Mar 3, 2025
f23c078
Update access isolation page
kosabogi Mar 3, 2025
991b02b
Merge branch 'main' into access-isolation-description
kosabogi Mar 3, 2025
1307b8c
Merge branch 'main' into access-isolation-description
kosabogi Mar 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...e/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to clarify what's the default, because this sentence is contradictory with the note, which was the only content of the original doc (https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-migration.html).

I believe the default now is isolation. In such case the introductory sentence might cause confusion.


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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
In {{ech}}, access isolation ensures that each deployment can only access its own snapshots, preventing accidental or unauthorized access to backups from other deployments within the same organization.
Any newly created deployment has snapshot isolation set up by default. These guides are only relevant for deployments created before this default was introduced, where deployments within your organization in the same region may 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.

::::{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.md)
* [AWS & GCP deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md)