You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the same issue after I initialized my AWS-credentials directly with the sdk and not explicitly passing them to the s3-uploader.
The problem here is that the s3-uploader always sets the aws-region when creating the S3-object. This is us-east-1 by default, which still supports the old aws-signature-version v2. However, newer regions do not support it anymore. You therefore always have to explicitly set your aws-region when initializing the Upload-object:
This solved the issue for me. Seems to me as if the aws-sdk still uses the endpoint you specified when updating your sdk-configuration although one can specify an alternative region when creating the S3-object. Anyway I hope this helps you as well.
Subject of the issue
Appear a error. InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
What is that?
Your environment
node --version
)identify -version
)Steps to reproduce
Tell us how to reproduce this issue. Please provide a minimal code example to demonstrate the problem.
// your code here
Expected behaviour
Tell us what should happen.
Actual behaviour
Tell us what happens instead.
// log outoput or error messages here
The text was updated successfully, but these errors were encountered: