Signature v4 Support
Opened this issue · 1 comments
Newly added regions only supports v4 signatures. What is sufficient to support this needs to be added to gulp-s3 since many will be using new regions in future. The lack of this feature may be one reason to get 400 FAILED responses.
+1 - I also am encountering the Sigv4 issue. According to Leek@AWS:
I suspect that the reason you are having issues is that all new AWS regions require Sigv4 signing for S3 requests - http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
You will notice the note on this page:
Amazon S3 supports Signature Version 4, a protocol for authenticating inbound API requests to AWS services, in all AWS regions. At this time, AWS regions created before January 30, 2014 will continue to support the previous protocol, Signature Version 2. Any new regions after January 30, 2014 will support only Signature Version 4 and therefore all requests to those regions must be made with Signature Version 4. For more information about AWS Signature Version 2, see Signing and Authenticating REST Requests in the Amazon Simple Storage Service Developer Guide.