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

S4cmd not working for DreamObjects or Other object storage services. #93

Closed
srinivas245 opened this issue Dec 31, 2016 · 4 comments
Closed

Comments

@srinivas245
Copy link

I just switched from s3cmd to s4cmd. It's working great for EC2 to Amazon S3 data transfer. But when I'm trying DreamObjects or CenturyLink Object storage in it's place, it shows the below error:

ClientError: An error occurred (InvalidAccessKeyId) when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.

I properly configured .s3cfg for DreamObjects, I know it because when I type s3cmd ls it lists the buckets. But when I type s4cmd ls it gives the above error.

So is s4cmd not compatible with other object storage services currently?

@vchrisb
Copy link

vchrisb commented Jan 24, 2017

had the same issue and it looks like s4cmd does not support the endpoint_url parameter.
There is a merge request though: #82

@navinpai
Copy link
Contributor

Dupe of #107


A pullrequest doing just this was merged into master a couple days back (#82 ). Should be fine to work with any endpoint using --endpoint-url. We're in the process of updating our test-suite to use minio to ensure this works E2E, but you can play around with it in the meantime! (You'll have to build from the latest code until we update pip et al)

Closing this issue for now, but let me know if you face any issues and I'll reopen it! :D

@Xp0is0nX
Copy link

Hi,
while "ls" operation seems to be working, "put" doesn't and end up with:

[Exception] Parameter validation failed:
Invalid length for parameter Key, value: 0, valid range: 1-inf
[Thread Failure] Parameter validation failed:
Invalid length for parameter Key, value: 0, valid range: 1-inf

@BrookeDot
Copy link

@Xp0is0nX I had that problem too but adding a / to the end of my bucket seemed to fix it. Ie s3://backups/ instead of s3://backups. You may have moved on but thought this may be worth mentioning.

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

No branches or pull requests

5 participants