source_profile in credentials file not used

[udf2457]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• [ x] I've gone though Developer Guide and API reference
• [ x] I've checked AWS Forums and StackOverflow for answers
• [ x] I've searched for previous similar issues and didn't find any solution

Describe the bug

Given the following credentials file (~/.aws/credentials):

[default]
aws_access_key_id = foo
aws_secret_access_key = bar

[foobar]
role_arn = arn:aws:iam::12345:role/foobar
external_id = barfoo
source_profile = default

And the following code:

creds := &credentials.SharedCredentialsProvider{Profile:config.CredentialsProfile }
	awsConfig := &aws.Config{Region: aws.String(config.Region),
		UseDualStack:                  aws.Bool(config.UseDualStack),
		CredentialsChainVerboseErrors: aws.Bool(config.Debug),
		LogLevel:                      aws.LogLevel(logLevel),
		Credentials: credentials.NewCredentials(creds)}
	awsOptions := &session.Options{Config: *awsConfig}
	sess, err := session.NewSessionWithOptions(*awsOptions)
	if err != nil {
		log.Fatal().Err(err)
	}

The following is reported in SDK Debug:
error SharedCredsAccessKey: shared credentials foobar in /Users/foo/.aws/credentials did not contain aws_access_key_id

Version of AWS SDK for Go?
1.35.35

Version of Go (go version)?

go version go1.15.5 darwin/amd64

To Reproduce (observed behavior)
See description

Expected behavior
source_profile should be honoured

Additional context

[skotambkar]

Thanks for reaching out. The issue here seems to be incorrect usage of SharedCredentialProvider.

Please take a look at https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/session#hdr-Creating_Sessions to see how to build session when working with ~/.aws/credentials

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.