Open
Conversation
Contributor
|
Can you use |
Author
|
Environment variable didn't work for me. The access error is still there. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
When connecting to public S3-buckets via
boto3, an access error occurred:To solve this problem it was necessary to add the parameter
signature_version=UNSIGNEDwhen creating the S3 client, which disables request signing, allowing access to public buckets without AWS keys.Сode changes:
In the S3 client initialization place (
utils.py),ConfigandUNSIGNEDare imported frombotocore.In the client constructor
client(‘s3’, ...)the argumentconfig=Config(signature_version=UNSIGNED)is passed.PR checklist:
scripts/format).scripts/lint).scripts/test).