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

Jump to bottom

Support S3 compatible object storage with AWS Signature V4 (Minio) #9640

Closed
cyberduck opened this issue Jul 31, 2016 · 4 comments
Closed

Support S3 compatible object storage with AWS Signature V4 (Minio) #9640

cyberduck opened this issue Jul 31, 2016 · 4 comments
Assignees
@dkocher
Labels
enhancement s3 AWS S3 Protocol Implementation worksforme
Milestone
5.1

Comments

@cyberduck
Copy link
Collaborator

8f042ae created the issue

Hi,
Minio (https://minio.io) is a open source Object Storage, compatible with AWS S3 signature V4. It will be great to have cyberduck support for community.

Our play server is available for public use, feel free to use it for all the test with details below.

  • URL: https://play.minio.io:9000
  • Access Key: Q3AM3UQ867SPQQA43P2F
  • Secret Key: zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG

Alternatively you can download Minio Server from (https://github.com/minio/minio) and associated documentation at (https://docs.minio.io/docs/minio-quickstart-guide)

We will be more than happy to work together and help for the same.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

This service sends a 400 The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. error message when attempting to authenticate using AWS2 which already makes Cyberduck switch to AWS4 signature version and subsequent authentication success.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Test in ffdc804.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

You will have to install the Generic S3 HTTPS profile to connect to non AWS endpoints.

@cyberduck
Copy link
Collaborator Author

8f042ae commented

Thanks,
We tested it works fine, if we had an option of making port editable under S3 it would have been fine. :)

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
enhancement s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Milestone
5.1
Development

No branches or pull requests
2 participants
@dkocher @cyberduck