-
Notifications
You must be signed in to change notification settings - Fork 233
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
Commit 2dad7e1f810369a2c3cff5453a309d2eefef3e68 makes s5cmd not working with S3-compatible services #251
Comments
We are experiencing the same thing, though we are using the docker image peakcom/s5cmd:v1.2.0. Prior to this we used s5cmd
|
I believe my issue is all about the same #252 |
For the record my own S3-compatible service is also a Ceph+RadosGW. |
this seems to fix it |
The code added for cross region support makes s5cmd not working anymore with S3-compatible services other than AWS.
Step to reproduce.
The simple "ls" command works fine. But trying to do "ls s3://bucket-name-here" will always result in 403 access denied.
The commit before this worked just as expected.
I have tested this with my own S3-compatible services and failed. Since it also occurred to DO Space I think the problem could be applied to any S3-compatible platform out there.
I also tried setting environment AWS_REGION and AWS_DEFAULT_REGION to "sgp1" but still not working.
The text was updated successfully, but these errors were encountered: