search

timkay / aws

Easy command line access to Amazon EC2, S3, SQS, ELB, and SDB
http://timkay.com/aws/
427 stars 126 forks source link

The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256 #112

Open aneeskA opened 8 years ago

aneeskA commented 8 years ago

I am seeing this error when I try to put or delete S3 bucket when the region chosen was ap-south-1

How can I fix this issue?

307 Temporary Redirect +----------------+----------------------------------------------------------------------------------------------+------------------+ | Code | Message | RequestId | +----------------+----------------------------------------------------------------------------------------------+------------------+ | InvalidRequest | The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. | 7971340917571523 | +----------------+----------------------------------------------------------------------------------------------+------------------+

timkay commented 8 years ago

Try adding --AWS4

My preference would have been to upgrade the authorization mechanism for everybody, but Amazon didn't create an upward compatible path everywhere.

...Tim

On Thu, Jul 14, 2016 at 9:28 AM, aneeskA notifications@github.com wrote:

I am seeing this error when I try to put or delete S3 bucket when the region chosen was ap-south-1

How can I fix this issue?

307 Temporary Redirect

+----------------+----------------------------------------------------------------------------------------------+------------------+ | Code | Message | RequestId |

+----------------+----------------------------------------------------------------------------------------------+------------------+ | InvalidRequest | The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. | 7971340917571523 |

+----------------+----------------------------------------------------------------------------------------------+------------------+

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/timkay/aws/issues/112, or mute the thread https://github.com/notifications/unsubscribe/AAD-eMNGGWlFMDt0C4_Jq8zztGoSHeeIks5qVmOkgaJpZM4JMnJ7 .

Tim Kay m: +1-650-248-0123 Skype: timkay

aneeskA commented 8 years ago

Thank you. I am very new to AWS. I came across Boto3 also. I am a little unsure what to use now.

aneeskA commented 8 years ago

Update:

I used the option --AWS4 . I am getting the following error

SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your key and signing method.

djwdjwdjwdjw commented 1 year ago

Is there a solution to AWS4-HMAC-SHA256 with this package?

timkay commented 1 year ago

I haven't been updating that "aws" command for over a decade. Amazon was never any help even though a lot of their users used it, and they have the AWS CLI now, which is clunkier but supported.

Sorry!

...Tim

On Fri, Jan 27, 2023 at 12:04 PM djwdjwdjwdjw @.***> wrote:

Is there a solution to AWS4-HMAC-SHA256 with this package?

— Reply to this email directly, view it on GitHub https://github.com/timkay/aws/issues/112#issuecomment-1407018104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAP46DTU2XWPQI3SMBD6S3WUQS6BANCNFSM4CJSOJ5Q . You are receiving this because you commented.Message ID: @.***>