Update snapshot-restore.md (#4656) (#5237)

* Update snapshot-restore.md Lessons learned from connecting it to a Scality * Update _tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md --------- (cherry picked from commit 7da94d2) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
opensearch-project · Oct 17, 2023 · 5769fe5 · 5769fe5
1 parent e410af4
commit 5769fe5
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md b/_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md
@@ -131,7 +131,7 @@ You will most likely not need to specify any parameters except for `location`. F
    s3.client.default.proxy.port: 8080 # port for your proxy server
    s3.client.default.read_timeout: 50s # the S3 connection timeout
    s3.client.default.use_throttle_retries: true # whether the client should wait a progressively longer amount of time (exponential backoff) between each successive retry
-   s3.client.default.region: us-east-2 # AWS region to use
+   s3.client.default.region: us-east-2 # AWS region to use. For non-AWS S3 storage, this value is required but has no effect.
    ```
 
 1. (Optional) If you don't want to use AWS access and secret keys, you could configure the S3 plugin to use AWS Identity and Access Management (IAM) roles for service accounts: