You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
You can use AWS S3 as a repository for [Snapshot/Restore](../snapshot-and-restore.md).
12
12
13
-
::::{note}
13
+
::::{note}
14
14
If you are looking for a hosted solution of Elasticsearch on AWS, please visit [https://www.elastic.co/cloud/](https://www.elastic.co/cloud/).
15
15
::::
16
16
@@ -122,7 +122,7 @@ The following list contains the available client settings. Those that must be st
122
122
`path_style_access`
123
123
: 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`.
124
124
125
-
::::{note}
125
+
::::{note}
126
126
:name: repository-s3-path-style-deprecation
127
127
128
128
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:
168
168
`base_path`
169
169
: 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 `/`.
170
170
171
-
::::{note}
171
+
::::{note}
172
172
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.
173
173
::::
174
174
@@ -192,7 +192,7 @@ The following settings are supported:
192
192
193
193
If `false`, the cluster can write to the repository and create snapshots in it. Defaults to `false`.
194
194
195
-
::::{important}
195
+
::::{important}
196
196
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.
197
197
198
198
::::
@@ -231,7 +231,7 @@ The following settings are supported:
231
231
`get_register_retry_delay`
232
232
: ([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`.
233
233
234
-
::::{note}
234
+
::::{note}
235
235
The option of defining client settings in the repository settings as documented below is considered deprecated, and will be removed in a future version.
236
236
::::
237
237
@@ -352,7 +352,7 @@ You may further restrict the permissions by specifying a prefix within the bucke
352
352
The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository registration will fail.
353
353
354
354
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]
356
356
357
357
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:
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`.
0 commit comments