Skip to content
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

"Error: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256." #31

Open
gazsp opened this issue May 8, 2017 · 7 comments

Comments

@gazsp
Copy link

gazsp commented May 8, 2017

This happens when I use s3-cli sync. Any ideas?

@KsenijaGogic
Copy link

@gazsp did you solve this?

@gazsp
Copy link
Author

gazsp commented Mar 5, 2018

@KsenijaGogic

Nope. Switched to using s3cmd.

@Soviut
Copy link

Soviut commented Oct 26, 2018

You can specify a region by doing the following

s3-cli sync --region=ca-central-1 /dist s3://my-bucket/

You'll also need to set the the following in ~/.aws/config

[default]
s3 =
  signature_version=s3v4

Note: The newline after the = followed by the indentation on the next line is intentional. It indicates a nested scope.

@Carl-Gustaf
Copy link

Thanks, adding the signature version to the config file did the job! Still I wonder whats the char after s3 = ?

@Carl-Gustaf
Copy link

Also make sure you add your region = [region] to your conf file if you run into signing issues

@biosthezerg
Copy link

Still I wonder whats the char after s3 = ?

There isn't one, the new line + indent means a nested scope is coming, it's kinda like YAML but with = instead of :

@Soviut
Copy link

Soviut commented Nov 2, 2022

@biosthezerg Thanks, I've updated my post just in case people don't scroll down far enough to read about the indentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants