AWS credentials not being read from ~/.aws/credentials about collector

[blablabla42]

I confirmed with following diff that using the default credentials provider exhibited the expected behaviour.

diff --git a/util/awsutil/amazon.go b/util/awsutil/amazon.go
index 5bf6f68..aa60c46 100644
--- a/util/awsutil/amazon.go
+++ b/util/awsutil/amazon.go
@@ -2,25 +2,12 @@ package awsutil
 
 import (
        "github.com/aws/aws-sdk-go/aws"
-       "github.com/aws/aws-sdk-go/aws/credentials"
-       "github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds"
-       "github.com/aws/aws-sdk-go/aws/ec2metadata"
        "github.com/aws/aws-sdk-go/aws/session"
        "github.com/pganalyze/collector/config"
 )
 
 func GetAwsSession(config config.ServerConfig) *session.Session {
-       var creds *credentials.Credentials
-
-       if config.AwsAccessKeyID != "" {
-               creds = credentials.NewStaticCredentials(config.AwsAccessKeyID, config.AwsSecretAccessKey, "")
-       } else {
-               creds = credentials.NewCredentials(&ec2rolecreds.EC2RoleProvider{
-                       Client: ec2metadata.New(session.New()),
-               })
-       }
-
-       return session.New(&aws.Config{Credentials: creds, Region: aws.String(config.AwsRegion)})
+       return session.New(&aws.Config{Region: aws.String(config.AwsRegion)})
 }

[lfittl]

Hi @blablabla42 - So just to confirm, you would then want to place the AWS credentials in the home directory of the pganalyze user?

(in the typical package-based setup there would be a dedicated pganalyze user)

I'm okay with supporting the config file here, however we'd need to maintain compatibility with specifying the access key in the config variables (i.e. not remove that logic altogether)

[blablabla42]

So just to confirm, you would then want to place the AWS credentials in the home directory of the pganalyze user?

Yeap, that's correct.

I'm okay with supporting the config file here, however we'd need to maintain compatibility with specifying the access key in the config variables (i.e. not remove that logic altogether)

Correct, the diff above doesn't address that. I think it's doable by modifying the default credentials chain to add the newStaticCredentials instead of overwriting the credentials chain.

[mgood]

It looks like if you just delete the else block it will leave cred = nil, which should have the intended effect.

Can you please also update the vendored SDK to support the latest credential chain? We're running the collector on ECS, so this would allow it to pick up the task role automatically.

[mgood]

To clarify, using the default credential chain would not only allow using ~/.aws/credentials, but also other standard ways the AWS SDK detects the credentials, including the EC2 and ECS metadata (which have different endpoints), and other mechanisms AWS may add in the future. So, this would be an extremely useful update.

[lfittl]

@mgood @blablabla42 Committed that change to master in 199630b and 3b9a829 - will make a new release soon that includes that.

Thanks for your input on this!