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.

Sign up for GitHub

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

Jump to bottom

Error during uploads to Openstack SWIFT S3 #325

Closed
rontrompert opened this issue Jul 14, 2021 · 2 comments · Fixed by #331
Closed

Error during uploads to Openstack SWIFT S3 #325

rontrompert opened this issue Jul 14, 2021 · 2 comments · Fixed by #331
Labels
non-aws Issue related to other S3-Compatible Services
Milestone
v2.0.0

Comments

@rontrompert
Copy link

rontrompert commented Jul 14, 2021 •
edited
Loading

Hi,

When I try to upload objects to our own Openstack SWIFT S3 setup I get the following error.

AWS_ACCESS_KEY_ID=access_key AWS_SECRET_ACCESS_KEY=secret key AWS_REGION=NL ./s5cmd --endpoint-url https://my.endpoint cp /path/to/file s3://bucket
ERROR "cp /path/to/file s3://bucket/file": AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'NL' status code: 400, request id: txb0926a6d6af64ec1b4056-0060eeb559, host id: txb0926a6d6af64ec1b4056-0060eeb559

This is with version 1.3.0. Using version 1.1.0 it just works. Somehow it seems that only us-east-1 is allowed.

Could this be fixed?

Btw. I am really impressed by the performance.

Cheers,

Ron
@seruman seruman mentioned this issue Jul 29, 2021
Merged
@Niek
Copy link

Niek commented Sep 15, 2021

Same issue here, the region seems to fall back to us-east-1 for some operations, even though AWS_REGION is specified correctly. Hopefully #331 can be merged soon.

@ilkinulas ilkinulas added this to the v2.0.0 milestone Sep 20, 2021
@seruman seruman mentioned this issue Sep 20, 2021
Closed
@seruman
Copy link
Member

seruman commented Sep 20, 2021

Sorry to hear you're having this issue. We plan to fix it in the following months on v2.0.0 since changes in #331 breaks users of auto region detection.

Closing for #320.

@seruman seruman closed this as completed Sep 20, 2021
@seruman seruman mentioned this issue Sep 20, 2021
Closed
igungor pushed a commit that referenced this issue Sep 30, 2021
@seruman
storage/s3: fix precedence of region detection (#331)
6fac3f1 
Co-authored-by: Aykut Farsak <aykutfarsak@gmail.com>

This PR makes changes to predecense of region detection as below;

```
1. --source-region or --destination-region flags of cp command.
2. AWS_REGION environment variable.
3. Region section of AWS profile.
4. Auto detection from bucket region (via HeadBucket).
5. us-east-1 as default region.
```

Resolves #325, resolves #320.

Closes #317.
@boraberke boraberke added the non-aws Issue related to other S3-Compatible Services label Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
non-aws Issue related to other S3-Compatible Services
Projects
None yet
Milestone
v2.0.0
Development

Successfully merging a pull request may close this issue.

storage/s3: fix precedence of region detection peak/s5cmd
5 participants
@Niek @ilkinulas @rontrompert @seruman @boraberke