Add missing mapped_pages

deploy-manage/cloud-organization/billing.md

@@ -2,6 +2,7 @@
 mapped_urls:
   - https://www.elastic.co/guide/en/cloud/current/ec-billing.html
   - https://www.elastic.co/guide/en/serverless/current/general-manage-billing.html
+  - https://www.elastic.co/guide/en/serverless/current/general-billing-stop-project.html
 applies_to:
   deployment:
     ess: all
@@ -21,7 +22,7 @@ Elastic charges a recurring fee for using our offerings on {{ecloud}}. In this s
   * [Elasticsearch projects](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md)
   * [Elastic Observability projects](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md)
   * [Elastic Security projects](/deploy-manage/cloud-organization/billing/security-billing-dimensions.md)
-  
+
 For more information, you can also refer to our [{{ech}}](https://www.elastic.co/pricing) and [{{serverless-full}}](https://www.elastic.co/pricing/serverless-search) pricing pages.
 
 ## Billing models

deploy-manage/tools/cross-cluster-replication.md

@@ -1,10 +1,12 @@
 ---
+mapped_pages:
+  - https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-ccr.html
 applies_to:
   deployment:
-    eck: 
-    ess: 
-    ece: 
-    self: 
+    eck:
+    ess:
+    ece:
+    self:
 ---
 
 # Cross-cluster replication [xpack-ccr]

deploy-manage/tools/snapshot-and-restore/create-snapshots.md

@@ -1,10 +1,12 @@
 ---
+mapped_pages:
+  - https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-take-snapshot.html
 applies_to:
   deployment:
-    eck: 
-    ess: 
-    ece: 
-    self: 
+    eck:
+    ess:
+    ece:
+    self:
 ---
 
 # Create snapshots [snapshots-take-snapshot]

deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md

@@ -2,9 +2,10 @@
 mapped_urls:
   - https://www.elastic.co/guide/en/cloud/current/ec-aws-custom-repository.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-custom-repository.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-aws-custom-repository.html
 applies_to:
   deployment:
-    ess: 
+    ess:
 ---
 
 # Configure a snapshot repository using AWS S3 [ec-aws-custom-repository]

deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md

@@ -1,7 +1,9 @@
 ---
+mapped_pages:
+  - https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-azure-migration.html
 applies_to:
   deployment:
-    ess: 
+    ess:
 ---
 
 # Repository isolation on Azure [ec-snapshot-repository-azure-migration]

deploy-manage/tools/snapshot-and-restore/restore-snapshot.md

@@ -1,10 +1,12 @@
 ---
+mapped_pages:
+  - https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html
 applies_to:
   deployment:
-    eck: 
-    ess: 
-    ece: 
-    self: 
+    eck:
+    ess:
+    ece:
+    self:
 ---
 
 # Restore a snapshot

deploy-manage/tools/snapshot-and-restore/s3-repository.md

@@ -1,16 +1,16 @@
---- 
+---
 mapped_urls:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/repository-s3.html
 applies_to:
   deployment:
-    self: 
+    self:
 ---
 
 # S3 repository [repository-s3]
 
 You can use AWS S3 as a repository for [Snapshot/Restore](../snapshot-and-restore.md).
 
-::::{note} 
+::::{note}
 If you are looking for a hosted solution of Elasticsearch on AWS, please visit [https://www.elastic.co/cloud/](https://www.elastic.co/cloud/).
 ::::
 
@@ -122,7 +122,7 @@ The following list contains the available client settings. Those that must be st
 `path_style_access`
 :   Whether to force the use of the path style access pattern. If `true`, the path style access pattern will be used. If `false`, the access pattern will be automatically determined by the AWS Java SDK (See [AWS documentation](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Builder.md#setPathStyleAccessEnabled-java.lang.Boolean-) for details). Defaults to `false`.
 
-::::{note} 
+::::{note}
 :name: repository-s3-path-style-deprecation
 
 In versions `7.0`, `7.1`, `7.2` and `7.3` all bucket operations used the [now-deprecated](https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/) path style access pattern. If your deployment requires the path style access pattern then you should set this setting to `true` when upgrading.
@@ -168,7 +168,7 @@ The following settings are supported:
 `base_path`
 :   Specifies the path to the repository data within its bucket. Defaults to an empty string, meaning that the repository is at the root of the bucket. The value of this setting should not start or end with a `/`.
 
-    ::::{note} 
+    ::::{note}
     Don’t set `base_path` when configuring a snapshot repository for {{ECE}}. {{ECE}} automatically generates the `base_path` for each deployment so that multiple deployments may share the same bucket.
     ::::
 
@@ -192,7 +192,7 @@ The following settings are supported:
 
     If `false`, the cluster can write to the repository and create snapshots in it. Defaults to `false`.
 
-    ::::{important} 
+    ::::{important}
     If you register the same snapshot repository with multiple clusters, only one cluster should have write access to the repository. Having multiple clusters write to the repository at the same time risks corrupting the contents of the repository.
 
     ::::
@@ -231,7 +231,7 @@ The following settings are supported:
 `get_register_retry_delay`
 :   ([time value](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/rest-apis/api-conventions.md#time-units)) Sets the time to wait before trying again if an attempt to read a [linearizable register](#repository-s3-linearizable-registers) fails. Defaults to `5s`.
 
-::::{note} 
+::::{note}
 The option of defining client settings in the repository settings as documented below is considered deprecated, and will be removed in a future version.
 ::::
 
@@ -352,7 +352,7 @@ You may further restrict the permissions by specifying a prefix within the bucke
 The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository registration will fail.
 
 
-#### Using IAM roles for Kubernetes service accounts for authentication [iam-kubernetes-service-accounts] 
+#### Using IAM roles for Kubernetes service accounts for authentication [iam-kubernetes-service-accounts]
 
 If you want to use [Kubernetes service accounts](https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/) for authentication, you need to add a symlink to the `$AWS_WEB_IDENTITY_TOKEN_FILE` environment variable (which should be automatically set by a Kubernetes pod) in the S3 repository config directory, so the repository can have the read access for the service account (a repository can’t read any files outside its config directory). For example:
 
@@ -361,7 +361,7 @@ mkdir -p "${ES_PATH_CONF}/repository-s3"
 ln -s $AWS_WEB_IDENTITY_TOKEN_FILE "${ES_PATH_CONF}/repository-s3/aws-web-identity-token-file"
 ```
 
-::::{important} 
+::::{important}
 The symlink must be created on all data and master eligible nodes and be readable by the `elasticsearch` user. By default, {{es}} runs as user `elasticsearch` using uid:gid `1000:0`.
 ::::
 

deploy-manage/tools/snapshot-and-restore/searchable-snapshots.md

@@ -1,10 +1,12 @@
 ---
+mapped_pages:
+  - https://www.elastic.co/guide/en/elasticsearch/reference/current/searchable-snapshots.html
 applies_to:
   deployment:
-    eck: 
-    ess: 
-    ece: 
-    self: 
+    eck:
+    ess:
+    ece:
+    self:
 ---
 
 # Searchable snapshots [searchable-snapshots]

reference/data-analysis/observability/observability-aws-metrics-serverless.md

@@ -1,6 +1,7 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-aws-metrics.html
+  - https://www.elastic.co/guide/en/observability/current/aws-metrics.html
 ---
 
 # AWS metrics [observability-aws-metrics]

reference/data-analysis/observability/observability-container-metrics-serverless.md

@@ -1,6 +1,7 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-container-metrics.html
+  - https://www.elastic.co/guide/en/observability/current/container-metrics.html
 ---
 
 # Container metrics [observability-container-metrics]

reference/data-analysis/observability/observability-host-metrics-serverless.md

@@ -1,6 +1,7 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-host-metrics.html
+  - https://www.elastic.co/guide/en/observability/current/host-metrics.html
 ---
 
 # Host metrics [observability-host-metrics]

reference/data-analysis/observability/observability-kubernetes-pod-metrics-serverless.md

@@ -1,6 +1,7 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-kubernetes-pod-metrics.html
+  - https://www.elastic.co/guide/en/observability/current/kubernetes-pod-metrics.html
 ---
 
 # Kubernetes pod metrics [observability-kubernetes-pod-metrics]

release-notes/elastic-security.md

@@ -2,23 +2,24 @@
 navigation_title: "Elastic Security"
 mapped_pages:
   - https://www.elastic.co/guide/en/security/master/release-notes-header-9.0.0.html
+  - https://www.elastic.co/guide/en/security/current/release-notes.html
 ---
 # Elastic Security release notes [elastic-security-release-notes]
 
-Review the changes, fixes, and more in each version of Elastic Security. 
+Review the changes, fixes, and more in each version of Elastic Security.
 
 To check for security updates, go to [Security announcements for the Elastic stack](https://discuss.elastic.co/c/announcements/security-announcements/31).
 
-% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections. 
+% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections.
 
 % ## version.next [elastic-security-next-release-notes]
 % **Release date:** Month day, year
 
 % ### Features and enhancements [elastic-security-next-features-enhancements]
-% * 
+% *
 
 % ### Fixes [elastic-security-next-fixes]
-% * 
+% *
 
 ## 9.0.0 [elastic-security-900-release-notes]
 **Release date:** March 25, 2025

solutions/observability/apps/configure-synthetics-settings.md

@@ -1,3 +1,9 @@
+---
+mapped_pages:
+  - https://www.elastic.co/guide/en/serverless/current/observability-synthetics-settings.html
+  - https://www.elastic.co/guide/en/observability/current/synthetics-settings.html
+---
+
 # Configure Synthetics settings [synthetics-settings]
 
 There are several Synthetics settings you can adjust in Observability.

troubleshoot/monitoring/unavailable-shards.md

@@ -1,7 +1,7 @@
 ---
 navigation_title: "Unavailable shards"
 mapped_urls:
-  - 
+  - https://www.elastic.co/guide/en/cloud/current/ec-scenario_why_are_shards_unavailable.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/echscenario_why_are_shards_unavailable.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-analyze_shards_with-api.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-analyze_shards_with-kibana.html