Skip to content

Add the Ability to Specify Region and Signer Override in S3 SDK #51861

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
original-brownbear opened this issue Feb 4, 2020 · 1 comment · Fixed by #52112
Closed

Add the Ability to Specify Region and Signer Override in S3 SDK #51861

original-brownbear opened this issue Feb 4, 2020 · 1 comment · Fixed by #52112
Assignees
@original-brownbear
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >enhancement

Comments

@original-brownbear
Copy link
Member

Some S3 compatible blob stores force v4 authentication with regions other than the default us-east-1 or don't support v4 authentication.
Currently there is no way of changing the signing region (we only allow setting the endpoint) or forcing the S3 SDK to not use v4 auth if the endpoint does not support it.

We should bring back the region setting to allow v4 auth to properly work if the blobstore supports it.
Also, we should expose the signer override setting to allow forcing the supported auth mechanism in case the SDK is unable to determine the correct one for a given endpoint.

Link: https://discuss.elastic.co/t/s3-snapshot-on-s3-compatible-servers/217750/4
@original-brownbear original-brownbear added >enhancement :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs labels Feb 4, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore)

@original-brownbear original-brownbear changed the title Add Ability to Specify Region and Signer Override in S3 SDK Add the Ability to Specify Region and Signer Override in S3 SDK Feb 4, 2020
@original-brownbear original-brownbear self-assigned this Feb 9, 2020
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this issue Feb 9, 2020
@original-brownbear
Add Region and Signer Algorithm Overrides to S3 Repos
c7ffbfc 
Closes elastic#51861
@original-brownbear original-brownbear mentioned this issue Feb 9, 2020
Merged
original-brownbear added a commit that referenced this issue Feb 20, 2020
@original-brownbear
Add Region and Signer Algorithm Overrides to S3 Repos (#52112)
c257b56 
Exposes S3 SDK signing region and algorithm override settings as requested in #51861.

Closes #51861
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this issue Feb 20, 2020
@original-brownbear
Add Region and Signer Algorithm Overrides to S3 Repos (elastic#52112)
13f02c4 
Exposes S3 SDK signing region and algorithm override settings as requested in elastic#51861.

Closes elastic#51861
@original-brownbear original-brownbear mentioned this issue Feb 20, 2020
Merged
original-brownbear added a commit that referenced this issue Feb 21, 2020
@original-brownbear
Add Region and Signer Algorithm Overrides to S3 Repos (#52112) (#52562)
1662cd4 
Exposes S3 SDK signing region and algorithm override settings as requested in #51861.

Closes #51861
@codebrain codebrain mentioned this issue Apr 1, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@original-brownbear original-brownbear

Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Region and Signer Algorithm Overrides to S3 Repos original-brownbear/elasticsearch
2 participants
@original-brownbear @elasticmachine