This repository was archived by the owner on Feb 26, 2025. It is now read-only.
Support for user-specified AWS credential providers#97
Open
thomascollett wants to merge 2 commits intoUpplication:masterfrom
Open
Support for user-specified AWS credential providers#97thomascollett wants to merge 2 commits intoUpplication:masterfrom
thomascollett wants to merge 2 commits intoUpplication:masterfrom
Conversation
17 tasks
|
Hi @thomascollett , I hope you're well! I'm not sure, if you've recieved my e-mail, but just in case -- I'm reaching out here as well. As this project seems to have been abandoned, I was wondering, if you'd be interested in contributing these fixes against our spin-off (rebranded fork) -- s3fs-nio? Kind regards, Martin |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for passing in a credentials provider using the
s3fs_credentials_providerproperty.This is useful if you are assuming a role, which requires refreshable credentials from STS using a
STSAssumeRoleSessionCredentialsProvider. This would enable segregation using a separate AWS role per customer, with each role only having permissions to access their own objects in the bucket.e.g.