Resolving comments

kosabogi · kosabogi · commit 30dddc064627 · 2025-02-20T11:22:55.000+01:00
diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml
@@ -431,16 +431,16 @@ toc:
                   - file: tools/snapshot-and-restore/ec-aws-custom-repository.md
                   - file: tools/snapshot-and-restore/ec-gcs-snapshotting.md
                   - file: tools/snapshot-and-restore/ec-azure-snapshotting.md
+                  - file: tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
+                    children:
+                      - file: tools/snapshot-and-restore/repository-isolation-on-azure.md
+                      - file: tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md
               - file: tools/snapshot-and-restore/cloud-enterprise.md
                 children:
                   - file: tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md
                   - file: tools/snapshot-and-restore/azure-storage-repository.md
                   - file: tools/snapshot-and-restore/minio-on-premise-repository.md
               - file: tools/snapshot-and-restore/cloud-on-k8s.md
-          - file: tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
-            children:
-              - file: tools/snapshot-and-restore/repository-isolation-on-azure.md
-              - file: tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md
           - file: tools/snapshot-and-restore/create-snapshots.md
           - file: tools/snapshot-and-restore/restore-snapshot.md
             children:
diff --git a/deploy-manage/tools/cross-cluster-replication.md b/deploy-manage/tools/cross-cluster-replication.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-ccr.html
-
 applies:
   stack: all
   hosted: all
diff --git a/deploy-manage/tools/snapshot-and-restore.md b/deploy-manage/tools/snapshot-and-restore.md
@@ -1,50 +1,13 @@
 ---
-mapped_urls:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-snapshot-restore.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-restoring-snapshots.html
-  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-snapshot-restore.html
-  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-restoring-snapshots.html
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-snapshots.html
-
 applies:
   stack: all
   hosted: all
   ece: all
-  eck: all
-  
+  eck: all 
 ---
 
 # Snapshot and restore
 
-% What needs to be done: Refine
-
-% GitHub issue: https://github.com/elastic/docs-projects/issues/343
-
-% Scope notes: Merge all articles to be relevant for all deployment types.
-
-% Use migrated content from existing pages that map to this page:
-
-% - [ ] ./raw-migrated-files/elasticsearch/elasticsearch-reference/snapshot-restore.md
-% - [ ] ./raw-migrated-files/cloud/cloud/ec-snapshot-restore.md
-% - [ ] ./raw-migrated-files/cloud/cloud/ec-restoring-snapshots.md
-%      Notes: redirect only
-% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-snapshot-restore.md
-% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-restoring-snapshots.md
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-snapshots.md
-
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
-
-$$$snapshot-repository-contents$$$
-
-$$$feature-state$$$
-
-$$$snapshot-restore-version-compatibility$$$
-
-$$$snapshots-shard-allocation$$$
-
-$$$fn-archive$$$
-
 A snapshot is a backup of a running Elasticsearch cluster. You can use snapshots to:
 
 - Regularly back up a cluster with no downtime
@@ -128,7 +91,7 @@ Snapshots don’t contain or back up:
 - Node configuration files
 - [Security configuration files](/deploy-manage/security.md)
 
-### Feature states
+### Feature states [feature-states]
 
 A **feature state** contains the indices and data streams used to store configurations, history, and other data for an Elastic feature, such as **Elasticsearch security** or **Kibana**.
 
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
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-migration.html
-  
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/azure-repository.md b/deploy-manage/tools/snapshot-and-restore/azure-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/repository-azure.html
-
 applies:
   stack: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/azure-storage-repository.md b/deploy-manage/tools/snapshot-and-restore/azure-storage-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-azure-snapshotting.html
-  
 applies:
   ece: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md
@@ -1,9 +1,5 @@
 ---
 navigation_title: "Elastic Cloud Enterprise"
-
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-repositories.html
-
 applies:
   ece: all
 ---
@@ -32,7 +28,7 @@ To configure Microsoft Azure Storage as a snapshot repository, refer to [Snapsho
 
 For more details about how snapshots are used with Elasticsearch, check [Snapshot and Restore](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html). You can also review the official documentation for these storage repository options:
 
-* [Amazon S3 documentation](http://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.md)
+* [Amazon S3 documentation](https://docs.aws.amazon.com/s3/)
 * [Microsoft Azure storage documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-quickstart-create-account)
 * [Google Cloud Storage documentation](https://cloud.google.com/storage/docs/)
 
diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md b/deploy-manage/tools/snapshot-and-restore/cloud-on-k8s.md
@@ -1,9 +1,5 @@
 ---
 navigation_title: "Elastic Cloud on Kubernetes"
-
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-snapshots.html
-
 applies:
   eck: all
 
diff --git a/deploy-manage/tools/snapshot-and-restore/create-snapshots.md b/deploy-manage/tools/snapshot-and-restore/create-snapshots.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-take-snapshot.html
-
 applies:
   stack: all
   hosted: all
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md b/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-aws-custom-repository.html
-  
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-azure-snapshotting.html
-
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-gcs-snapshotting.html
-
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/ece-restore-across-clusters.md b/deploy-manage/tools/snapshot-and-restore/ece-restore-across-clusters.md
@@ -1,15 +1,12 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restore-across-clusters.html
-
 applies:
   hosted: all
   ece: all
 ---
 
 # Restore a snapshot across clusters [ece-restore-across-clusters]
 
-Snapshots can be restored to either the same Elasticsearch cluster or to another cluster. If you are restoring all indices to another cluster, you can *clone* a cluster.
+Snapshots can be restored to either the same Elasticsearch cluster or to another cluster. If you are restoring all indices to another cluster, you can [clone](/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.html) a cluster.
 
 ::::{note} 
 Users created using the X-Pack security features or using Shield are not included when you restore across clusters, only data from Elasticsearch indices is restored. If you do want to create a cloned cluster with the same users as your old cluster, you need to recreate the users manually on the new cluster.
diff --git a/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-containing-searchable-snapshots-indices-across-clusters.md b/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-containing-searchable-snapshots-indices-across-clusters.md
@@ -1,8 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restore-snapshots-containing-searchable-snapshots-indices-across-clusters.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-restore-snapshots-containing-searchable-snapshots-indices-across-clusters.html
-
 applies:
   hosted: all
   ece: all
diff --git a/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-existing-deployment.md b/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-existing-deployment.md
@@ -1,8 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restore-snapshots-into-existing-deployment.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-restore-snapshots-into-existing-deployment.html
-
 applies:
   hosted: all
   ece: all
diff --git a/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md b/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md
@@ -1,8 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restore-snapshots-into-new-deployment.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-restore-snapshots-into-new-deployment.html
-
 applies:
   hosted: all
   ece: all
diff --git a/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md b/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md
@@ -1,34 +1,11 @@
 ---
 navigation_title: "Elastic Cloud Hosted"
-mapped_urls:
-  - https://www.elastic.co/guide/en/cloud/current/ec-custom-repository.html
-  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-custom-repository.html
-
 applies:
   hosted: all
 ---
 
 # Manage snapshot repositories in Elastic Cloud Hosted
 
-% What needs to be done: Lift-and-shift
-
-% Use migrated content from existing pages that map to this page:
-
-% - [ ] ./raw-migrated-files/cloud/cloud/ec-custom-repository.md
-%      Notes: 3 children
-% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-custom-repository.md
-%      Notes: redirects only
-
-=======
-
-⚠️ **This page is a work in progress.** ⚠️
-
-The documentation team is working to combine content pulled from the following pages:
-
-* [/raw-migrated-files/cloud/cloud/ec-custom-repository.md](/raw-migrated-files/cloud/cloud/ec-custom-repository.md)
-* [/raw-migrated-files/cloud/cloud-heroku/ech-custom-repository.md](/raw-migrated-files/cloud/cloud-heroku/ech-custom-repository.md)
-
-
 Snapshot repositories allow you to back up and restore your Elasticsearch data efficiently. In Elastic Cloud Hosted, repositories are automatically registered and managed within your deployment, ensuring data security, long-term archiving, and seamless recovery.
 
 By default, Elastic Cloud Hosted takes a snapshot of all the indices in your Elasticsearch cluster every 30 minutes. You can set a different snapshot interval if needed for your environment. You can also take snapshots on demand, without having to wait for the next interval. Taking a snapshot on demand does not affect the retention schedule for existing snapshots; it just adds an additional snapshot to the repository. This might be helpful if you are about to make a deployment change and you don’t have a current snapshot.
@@ -61,11 +38,11 @@ When working with snapshot repositories in Elastic Cloud Hosted, keep the follow
 
 ## Elastic Cloud Hosted snapshot repository types [ess-repo-types]
 
-[Elastic Cloud Hosted deployments](https://cloud.elastic.co/registration?page=docs&placement=docs-body) automatically register the [`found-snapshots`](../snapshot-and-restore.md) repository. {{ess}} uses this repository and the `cloud-snapshot-policy` to take periodic snapshots of your cluster. You can also use the `found-snapshots` repository for your own [{{slm-init}} policies](create-snapshots.md#automate-snapshots-slm) or to store searchable snapshots.
+[Elastic Cloud Hosted deployments](https://cloud.elastic.co/registration?page=docs&placement=docs-body) automatically register the [`found-snapshots`](../snapshot-and-restore.md) repository. {{ech}} uses this repository and the `cloud-snapshot-policy` to take periodic snapshots of your cluster. You can also use the `found-snapshots` repository for your own [{{slm-init}} policies](create-snapshots.md#automate-snapshots-slm) or to store searchable snapshots.
 
 The `found-snapshots` repository is specific to each deployment. However, you can restore snapshots from another deployment’s `found-snapshots` repository if the deployments are under the same account and in the same region. See the Cloud [Snapshot and restore](../snapshot-and-restore.md) documentation to learn more.
 
-{{ess}} deployments also support the following repository types:
+{{ech}} deployments also support the following repository types:
 
 * [Azure](ec-azure-snapshotting.md)
 * [Google Cloud Storage](ec-gcs-snapshotting.md)
diff --git a/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md b/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-gcp-snapshotting.html
-  
 applies:
   ece: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-repository.md b/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/repository-gcs.html
-
 applies:
   stack: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/manage-snapshot-repositories.md b/deploy-manage/tools/snapshot-and-restore/manage-snapshot-repositories.md
@@ -1,21 +1,13 @@
 ---
-
 applies:
   stack: all
   hosted: all
   ece: all
   eck: all
-
 ---
 
 # Manage snapshot repositories
 
-% What needs to be done: Write from scratch
-
-% GitHub issue: https://github.com/elastic/docs-projects/issues/343
-
-% Scope notes: Landing page for this containing links for Cloud and ECE
-
 Snapshot repositories allow you to back up and restore your Elasticsearch data efficiently. Whether you're using [{{ech}}](#elastic-cloud-hosted), [{{ece}} (ECE)](#elastic-cloud-enterprise-ece), [{{eck}} (ECK)](#elastic-cloud-on-kubernetes-eck), or managing your own [{{es}} cluster](#self-managed), configuring a snapshot repository ensures data security, long-term archiving, and seamless migration across environments.
 
 ## Supported repository types
diff --git a/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md b/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configuring-minio.html
-
 applies:
   ece: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md b/deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md
@@ -1,15 +1,12 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-read-only-repository.html
-  
 applies:
   stack: all
 ---
 
 # Read-only URL repository [snapshots-read-only-repository]
 
 ::::{note} 
-This repository type is only available if you run {{es}} on your own hardware. If you use {{ess}}, see [{{ess}} repository types](self-managed.md).
+This repository type is only available if you run {{es}} on your own hardware. If you use {{ech}}, see [{{ech}} repository types](self-managed.md).
 ::::
 
 
diff --git a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-aws-gcp-migration.html
-
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md
@@ -1,7 +1,4 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-azure-migration.html
-
 applies:
   hosted: all
 ---
diff --git a/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md b/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md
diff --git a/deploy-manage/tools/snapshot-and-restore/s3-repository.md b/deploy-manage/tools/snapshot-and-restore/s3-repository.md
diff --git a/deploy-manage/tools/snapshot-and-restore/searchable-snapshots.md b/deploy-manage/tools/snapshot-and-restore/searchable-snapshots.md
diff --git a/deploy-manage/tools/snapshot-and-restore/self-managed.md b/deploy-manage/tools/snapshot-and-restore/self-managed.md
diff --git a/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md b/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md
diff --git a/deploy-manage/tools/snapshot-and-restore/source-only-repository.md b/deploy-manage/tools/snapshot-and-restore/source-only-repository.md
