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

Can't sync keys within one bucket? #12

Closed
NickStefan opened this issue May 30, 2019 · 1 comment
Closed

Can't sync keys within one bucket? #12

NickStefan opened this issue May 30, 2019 · 1 comment

Comments

@NickStefan
Copy link

NickStefan commented May 30, 2019

EDIT for clarity:
I'm able to use the aws CLI and keys like this:

aws --endpoint-url https://s3.amazonaws.com s3 sync s3://bucket/key s3://bucket/other_key

But when I try something similar here

s3sync --tk KEY --ts SECRET --tr us-west-1 --sk KEY --ss SECRET --sr us-west-1 --se https://us-west-1.s3.amazonaws.com --te https://us-west-1.s3.amazonaws.com s3://BUCKET/key/ s3://BUCKET/OTHER_KEY/ -d

I get an error about The authorization header is malformed; the region 'us-west-1' is wrong; expecting 'us-east-1'

Synced: 0; Skipped: 0; Failed: 0; Total processed: 0onHeaderMalformed: The authorization header is malformed; the region 'us-west-1' is wrong; expecting 'us-east-1'

I'm 1000% sure my bucket is in us-west-1. The command works with aws cli. The keys work. The S3 bucket is in us-west-1. Any idea what the issue might be?

@NickStefan
Copy link
Author

NickStefan commented May 30, 2019

I dunno. I removed the --se and --te custom endpoints and it magically worked? I tried all sorts of combinations of endpoints:

https://s3.amazonaws.com
https:/us-west-1.s3.amazonaws.com
etc...

I feel like it should work with one of those? But I might be missing something. Apologies for the issue.

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

1 participant