-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
feature request: minio secret backend #2274
Comments
Based on minio/minio#3581 it seems like this is something that isn't even supported in minio and with no plans to support it, so closing. |
Minio apparently changed their stance near the end of 2018, there is now support for multiple users and bucket policies in the Minio object storage server. vault-plugin-secrets-minio was my attempt to do this for my home usage of Minio. |
@kula : any plans to make it core the last 6months ? Cheers for the plugin, i am gonna try it asap, just wondering for production purposes |
This would really be great. Minio has good policy and user features now. They also have a kms which integrates well with vault https://docs.min.io/docs/minio-kms-quickstart-guide.html for encrypting objects. So it would be really be nice to have vault as a central source for everything. |
Seeing as this issue is closed should a new issue be made or can this be reopened? |
I just wanted to +1 this. I know my employer would love this being officially supported too! |
+1 |
Can MinIO be used as IAM/ STS endpoint in Vault AWS auth method? |
+1 |
I think it would be beautiful to have vault include a minio (S3 like cloud object storage) secret backend so that you could carve up access to certain buckets to certain policies. This essentially adds S3 like ACLs to minio. You could also use vault to encrypt the objects as well.
The text was updated successfully, but these errors were encountered: