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

use s3 client directly #80

Closed
arschles opened this issue Jan 5, 2016 · 3 comments
Closed

use s3 client directly #80

arschles opened this issue Jan 5, 2016 · 3 comments
Assignees
Milestone

Comments

@arschles
Copy link
Member

arschles commented Jan 5, 2016

after #72, use minio-go or the official AWS Go SDK instead of calling to the mc binary directly. this will also remove the need to set the DOCKERIMAGE=1 env var in the docker image

@arschles arschles self-assigned this Jan 5, 2016
@arschles arschles added this to the v2.0-beta1 milestone Jan 5, 2016
@bacongobbler
Copy link
Member

I've been making leaps and bounds with getting boto3 working with minio. Would https://github.com/aws/aws-sdk-go be a potential viable alternative? It could initially be a pain, but migration from minio -> S3 -> riakcs would be a lot easier, I'd imagine

We can talk about this in Boulder next week if it interests you :)

@arschles
Copy link
Member Author

@bacongobbler yes, absolutely that is a viable alternative, and I've added it as an option in the description. I believe that we should support v2, v3 and v4 signatures so we can support older object stores, or stores like GCS that only offer v2 signatures at this time.

And yea, this interests me, so let's talk in Boulder.

@arschles
Copy link
Member Author

note for later, minio-go supports v2 and v4 signature versions, which means that it can support Riak CS

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

2 participants