oyd
/
minio
6
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added note to help differentiate MINIO creds from S3 rotating creds (#9887)

Browse Source
master
Benjamin Sodenkamp 4 years ago committed by GitHub
parent 972d876ca9
commit 0becf7f03f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 2
      docs/gateway/s3.md

2
docs/gateway/s3.md
Unescape View File

@ -22,6 +22,8 @@ minio gateway s3
### Using Binary in EC2 ### Using Binary in EC2
Using IAM rotating credentials for AWS S3 Using IAM rotating credentials for AWS S3
If you are using an S3 enabled IAM role on an EC2 instance for S3 access, MinIO will still require env vars MINIO_ACCESS_KEY and MINIO_SECRET_KEY to be set for its internal use. These may be set to any value which meets the length requirements. Access key length should be at least 3, and secret key length at least 8 characters.
``` ```
export MINIO_ACCESS_KEY=custom_access_key export MINIO_ACCESS_KEY=custom_access_key
export MINIO_SECRET_KEY=custom_secret_key export MINIO_SECRET_KEY=custom_secret_key

Write Preview
Loading…
Cancel
Save