-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Support for AWS Signature Version 4 #3
Comments
Cheers @michaelthorne, it looks like Might need to refactor using |
@adrianfalleiro that would be awesome! |
@michaelthorne can you try with the You can install it by running If it's working for you, I'll clean up and publish to npm |
@adrianfalleiro thanks for the quick update! I got the following error after installing it as per your comment above:
FYI, using |
Cheers @michaelthorne. I've fixed that issue with the error messaging. However I haven't done any testing for uploading gzipped files so that might also be an issue. I see gulp-gzip in that stack trace. Are you gzipping files? |
Ok got it working with gzip. Can you try again and let me know if working. Cheers |
Tested and released on npm as 2.0.0. |
This is also an issue in the gulp-s3 plugin, but mentioning it here too.
I've been unable to upload to certain (newer) S3 regions and it is as a result of them only supporting V4. i.e.
eu-west-2
(London) as a region, returns an ambiguous HTTP 400 error when attempting to publish files to a bucket in that region.If I only switch the region to e.g.
us-east-1
(formerly US Standard which supports V2 and V4) and leave everything else as is, the publish works as expected.The text was updated successfully, but these errors were encountered: