5 Commits

Author	SHA1	Message	Date
Harshavardhana	bd25f31100	Use IAM creds only if endpoint is S3 (#7111) ... Requirements like being able to run minio gateway in ec2 pointing to a Minio deployment wouldn't work properly because IAM creds take precendence on ec2. Add checks such that we only enable AWS specific features if our backend URL points to actual AWS S3 not S3 compatible endpoints.	2019-01-23 11:12:33 -08:00
Alex Simenduev	6dd8a83c5a	change credential chain order in s3 gateway to mimic official docs (#7091)	2019-01-17 10:31:51 -08:00
Jay Mundrawala	052a7b8eec	Allow minio s3 gateway to use different AWS auth mechanisms (#6422) ... Allow minio s3 gateway to use aws environment credentials, IAM instance credentials, or AWS file credentials. If AWS_ACCESS_KEY_ID, AWS_SECRET_ACCSES_KEY are set, or minio is running on an ec2 instance with IAM instance credentials, or there is a file $HOME/.aws/credentials, minio running as an S3 gateway will authenticate with AWS S3 using those one of credentials. The lookup order: 1. AWS environment varaibles 2. IAM instance credentials 3. $HOME/.aws/credentials 4. minio environment variables To authenticate with the minio gateway, you will always use the minio environment variables MINIO_ACCESS_KEY MINIO_SECRET_KEY.	2018-09-19 18:05:30 +05:30
Anis Elleuch	d524924b80	Fix gateway s3 doc to run custom S3 endpoint (#6369) ... To pass a custom S3 endpoint in S3 gateway, the user needs to specify it as an argument after 'minio gateway s3' and not as '--address' option since this latter specifies the address to which the gateway should listen.	2018-08-28 10:09:07 +05:30
Nitish Tiwari	b8f4f26cf6	Add S3 gateway documentation (#6165) ... Fixes #4830	2018-07-19 11:54:38 -07:00