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
Using libs3 in us-east-1, us-west-1 and 2 work for us, but us-east-2 fails. We get Error: S3 Copy Failed : The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
Is there a way to force V4 authorization for these newer regions.
The following regions don't support Signature Version 2. You must use Signature Version 4 to sign API requests in these regions:
US East (Ohio) Region
Canada (Central) Region
Asia Pacific (Mumbai) Region
Asia Pacific (Seoul) Region
EU (Frankfurt) Region
EU (London) Region
China (Beijing) Region
The text was updated successfully, but these errors were encountered:
Make sure you are you are correctly setting the bucket_context.authRegion (in your case, set it to "us-east-2"). Not setting that member will cause these kind of errors in V4 environments.
Using libs3 in us-east-1, us-west-1 and 2 work for us, but us-east-2 fails. We get Error: S3 Copy Failed : The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
Is there a way to force V4 authorization for these newer regions.
The following regions don't support Signature Version 2. You must use Signature Version 4 to sign API requests in these regions:
US East (Ohio) Region
Canada (Central) Region
Asia Pacific (Mumbai) Region
Asia Pacific (Seoul) Region
EU (Frankfurt) Region
EU (London) Region
China (Beijing) Region
The text was updated successfully, but these errors were encountered: