Adds V4 support so now works on all AWS regions #36
Conversation
This file contains 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
|
Could this be merged ? |
|
Can version 1.3.1 be published on npm? https://www.npmjs.com/package/aws-s3-zipper it still shows 1.3.0. |
|
@DanielHindi Could you please push 1.3.1 version to npm? |
|
done |
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.
Resolves #35
Error:
InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.Due to the fact that all regions support V4, but US-Standard, and many -- but not all -- other regions, also support the other, older scheme, Signature Version 2 ("V2"). Currently using V2 method. See stackoverflow for more details.