|
@@ -141,8 +141,9 @@ use `S3SignerType`, which is Signature Version 2.
|
|
|
===== Read timeout
|
|
|
|
|
|
Read timeout determines the amount of time to wait for data to be transferred over an established,
|
|
|
-open connection before the connection is timed out. By default,it is set to 50 seconds.
|
|
|
-It can be configured with `cloud.aws.read_timeout` setting:
|
|
|
+open connection before the connection is timed out.
|
|
|
+It can be configured with `cloud.aws.read_timeout` (or `cloud.aws.s3.read_timeout`) setting:
|
|
|
+
|
|
|
[source, yaml]
|
|
|
----
|
|
|
cloud.aws.read_timeout: 30s
|
|
@@ -264,12 +265,6 @@ The following settings are supported:
|
|
|
The default behaviour is to detect which access style to use based on the configured endpoint (an IP will result
|
|
|
in path-style access) and the bucket being accessed (some buckets are not valid DNS names).
|
|
|
|
|
|
-
|
|
|
-`read_timeout`::
|
|
|
-
|
|
|
- The amount of time to wait for data to be transferred over an established,
|
|
|
- open connection before the connection is timed out. Default to value of `cloud.aws.read_timeout`.
|
|
|
-
|
|
|
Note that you can define S3 repository settings for all S3 repositories in `elasticsearch.yml` configuration file.
|
|
|
They are all prefixed with `repositories.s3.`. For example, you can define compression for all S3 repositories
|
|
|
by setting `repositories.s3.compress: true` in `elasticsearch.yml`.
|