Skip to content

Commit b782c7d

Browse files
add missing mapped_pages
1 parent b3dc996 commit b782c7d

15 files changed

+56
-33
lines changed

deploy-manage/cloud-organization/billing.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
mapped_urls:
33
- https://www.elastic.co/guide/en/cloud/current/ec-billing.html
44
- https://www.elastic.co/guide/en/serverless/current/general-manage-billing.html
5+
- https://www.elastic.co/guide/en/serverless/current/general-billing-stop-project.html
56
applies_to:
67
deployment:
78
ess: all
@@ -21,7 +22,7 @@ Elastic charges a recurring fee for using our offerings on {{ecloud}}. In this s
2122
* [Elasticsearch projects](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md)
2223
* [Elastic Observability projects](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md)
2324
* [Elastic Security projects](/deploy-manage/cloud-organization/billing/security-billing-dimensions.md)
24-
25+
2526
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.
2627

2728
## Billing models

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

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-ccr.html
24
applies_to:
35
deployment:
4-
eck:
5-
ess:
6-
ece:
7-
self:
6+
eck:
7+
ess:
8+
ece:
9+
self:
810
---
911

1012
# Cross-cluster replication [xpack-ccr]

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

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-take-snapshot.html
24
applies_to:
35
deployment:
4-
eck:
5-
ess:
6-
ece:
7-
self:
6+
eck:
7+
ess:
8+
ece:
9+
self:
810
---
911

1012
# Create snapshots [snapshots-take-snapshot]

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22
mapped_urls:
33
- https://www.elastic.co/guide/en/cloud/current/ec-aws-custom-repository.html
44
- https://www.elastic.co/guide/en/cloud-heroku/current/ech-custom-repository.html
5+
- https://www.elastic.co/guide/en/cloud-heroku/current/ech-aws-custom-repository.html
56
applies_to:
67
deployment:
7-
ess:
8+
ess:
89
---
910

1011
# Configure a snapshot repository using AWS S3 [ec-aws-custom-repository]

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/cloud/current/ec-snapshot-repository-azure-migration.html
24
applies_to:
35
deployment:
4-
ess:
6+
ess:
57
---
68

79
# Repository isolation on Azure [ec-snapshot-repository-azure-migration]

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

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html
24
applies_to:
35
deployment:
4-
eck:
5-
ess:
6-
ece:
7-
self:
6+
eck:
7+
ess:
8+
ece:
9+
self:
810
---
911

1012
# Restore a snapshot

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
1-
---
1+
---
22
mapped_urls:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/repository-s3.html
44
applies_to:
55
deployment:
6-
self:
6+
self:
77
---
88

99
# S3 repository [repository-s3]
1010

1111
You can use AWS S3 as a repository for [Snapshot/Restore](../snapshot-and-restore.md).
1212

13-
::::{note}
13+
::::{note}
1414
If you are looking for a hosted solution of Elasticsearch on AWS, please visit [https://www.elastic.co/cloud/](https://www.elastic.co/cloud/).
1515
::::
1616

@@ -122,7 +122,7 @@ The following list contains the available client settings. Those that must be st
122122
`path_style_access`
123123
: 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`.
124124

125-
::::{note}
125+
::::{note}
126126
:name: repository-s3-path-style-deprecation
127127

128128
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:
168168
`base_path`
169169
: 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 `/`.
170170

171-
::::{note}
171+
::::{note}
172172
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.
173173
::::
174174

@@ -192,7 +192,7 @@ The following settings are supported:
192192

193193
If `false`, the cluster can write to the repository and create snapshots in it. Defaults to `false`.
194194

195-
::::{important}
195+
::::{important}
196196
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.
197197

198198
::::
@@ -231,7 +231,7 @@ The following settings are supported:
231231
`get_register_retry_delay`
232232
: ([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`.
233233

234-
::::{note}
234+
::::{note}
235235
The option of defining client settings in the repository settings as documented below is considered deprecated, and will be removed in a future version.
236236
::::
237237

@@ -352,7 +352,7 @@ You may further restrict the permissions by specifying a prefix within the bucke
352352
The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository registration will fail.
353353

354354

355-
#### Using IAM roles for Kubernetes service accounts for authentication [iam-kubernetes-service-accounts]
355+
#### Using IAM roles for Kubernetes service accounts for authentication [iam-kubernetes-service-accounts]
356356

357357
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:
358358

@@ -361,7 +361,7 @@ mkdir -p "${ES_PATH_CONF}/repository-s3"
361361
ln -s $AWS_WEB_IDENTITY_TOKEN_FILE "${ES_PATH_CONF}/repository-s3/aws-web-identity-token-file"
362362
```
363363

364-
::::{important}
364+
::::{important}
365365
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`.
366366
::::
367367

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

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/elasticsearch/reference/current/searchable-snapshots.html
24
applies_to:
35
deployment:
4-
eck:
5-
ess:
6-
ece:
7-
self:
6+
eck:
7+
ess:
8+
ece:
9+
self:
810
---
911

1012
# Searchable snapshots [searchable-snapshots]

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/serverless/current/observability-aws-metrics.html
4+
- https://www.elastic.co/guide/en/observability/current/aws-metrics.html
45
---
56

67
# AWS metrics [observability-aws-metrics]

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/serverless/current/observability-container-metrics.html
4+
- https://www.elastic.co/guide/en/observability/current/container-metrics.html
45
---
56

67
# Container metrics [observability-container-metrics]

0 commit comments

Comments
 (0)