MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2025-05-23 10:31:51 -04:00
Code Issues Packages Projects Releases Wiki Activity

change credential chain order in s3 gateway to mimic official docs (#7091)

Browse Source
This commit is contained in:
Alex Simenduev 2019-01-17 20:31:51 +02:00 committed by kannappanr
parent 1a7e6d4768
commit 6dd8a83c5a
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cmd/gateway/s3/gateway-s3.go
View File

@ -182,19 +182,19 @@ func newS3(url string) (*miniogo.Core, error) {
// Chains all credential types, in the following order: // Chains all credential types, in the following order:
// - AWS env vars (i.e. AWS_ACCESS_KEY_ID) // - AWS env vars (i.e. AWS_ACCESS_KEY_ID)
// - AWS creds file (i.e. AWS_SHARED_CREDENTIALS_FILE or ~/.aws/credentials)
// - IAM profile based credentials. (performs an HTTP // - IAM profile based credentials. (performs an HTTP
// call to a pre-defined endpoint, only valid inside // call to a pre-defined endpoint, only valid inside
// configured ec2 instances) // configured ec2 instances)
// - AWS creds file (i.e. AWS_SHARED_CREDENTIALS_FILE or ~/.aws/credentials)
// - Static credentials provided by user (i.e. MINIO_ACCESS_KEY) // - Static credentials provided by user (i.e. MINIO_ACCESS_KEY)
creds := credentials.NewChainCredentials([]credentials.Provider{ creds := credentials.NewChainCredentials([]credentials.Provider{
&credentials.EnvAWS{}, &credentials.EnvAWS{},
&credentials.FileAWSCredentials{},
&credentials.IAM{ &credentials.IAM{
Client: &http.Client{ Client: &http.Client{
Transport: minio.NewCustomHTTPTransport(), Transport: minio.NewCustomHTTPTransport(),
}, },
}, },
&credentials.FileAWSCredentials{},
&credentials.EnvMinio{}, &credentials.EnvMinio{},
}) })

2
docs/gateway/s3.md
View File

@ -31,8 +31,8 @@ minio gateway s3
Minio gateway will automatically look for list of credential styles in following order. Minio gateway will automatically look for list of credential styles in following order.
- AWS env vars (i.e. AWS_ACCESS_KEY_ID) - AWS env vars (i.e. AWS_ACCESS_KEY_ID)
- IAM profile based credentials. (performs an HTTP call to a pre-defined endpoint, only valid inside configured ec2 instances)
- AWS creds file (i.e. AWS_SHARED_CREDENTIALS_FILE or ~/.aws/credentials) - AWS creds file (i.e. AWS_SHARED_CREDENTIALS_FILE or ~/.aws/credentials)
- IAM profile based credentials. (performs an HTTP call to a pre-defined endpoint, only valid inside configured ec2 instances)
## Run Minio Gateway for AWS S3 compatible services ## Run Minio Gateway for AWS S3 compatible services
As a prerequisite to run Minio S3 gateway on an AWS S3 compatible service, you need valid access key, secret key and service endpoint. As a prerequisite to run Minio S3 gateway on an AWS S3 compatible service, you need valid access key, secret key and service endpoint.