-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat: add support for a credentials chain for minio access #31051
Conversation
If a static access key id and secret are not provided, instead fallback to a pulling credentials from other places, in priority order: 1. MINIO_ prefixed environment variables 2. AWS_ prefixed environment variables 3. a minio credentials file 4. an aws credentials file 5. EC2 instance metadata This enables using temporary credentials that are auto-refreshed upon expiration.
Thanks! Would you be able to add this to the documentation (app.ini example and config cheatsheet) as well? (the body of the PR is more than suitable to be used) |
I updated the en-us config cheatsheet and app.ini example to document the changes in minio credentials logic. I don't know how to translate this for the zh-cn config cheatsheet. Is there a process for translating these? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding the zh-CN:
Nope, unfortunately not yet.
Can we have a test? |
1cbf1ae
to
79a01e9
Compare
79a01e9
to
1a4127f
Compare
I added a test that verifies correct credentials are pulled from all of the possible credential providers in the chain. |
We wanted to be able to use the IAM role provided by the EC2 instance metadata in order to access S3 via the Minio configuration. To do this, a new credentials chain is added that will check the following locations for credentials when an access key is not provided. In priority order, they are: