You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running terraform with AWS_PROFILE=foobar, where foobar defines credential_source = Ec2InstanceMetadata in the ~/.aws/credentials works, because the auth happens natively via the go-sdk (see: https://github.com/aws/aws-sdk-go/pull/2201/files).
However, if I specify profile in terraform itself (either backend, or provider), then unfortunately a slimmed-down version of the aws-sdk is being used (https://github.com/hashicorp/aws-sdk-go-base/blob/master/awsauth.go) where it does not properly parse credentials_source from the aws-config and thus profile switching fails.
not sure why my previous bug was closed down. This is not a bug report on aws-provider but this is a bug on the s3 remote backend which is implemented in this repository.
Please do not close this ticket. It is a valid bug.
The text was updated successfully, but these errors were encountered:
running terraform with
AWS_PROFILE=foobar, wherefoobardefinescredential_source = Ec2InstanceMetadatain the~/.aws/credentialsworks, because the auth happens natively via the go-sdk (see: https://github.com/aws/aws-sdk-go/pull/2201/files).However, if I specify
profilein terraform itself (either backend, or provider), then unfortunately a slimmed-down version of the aws-sdk is being used (https://github.com/hashicorp/aws-sdk-go-base/blob/master/awsauth.go) where it does not properly parsecredentials_sourcefrom the aws-config and thus profile switching fails.not sure why my previous bug was closed down. This is not a bug report on aws-provider but this is a bug on the s3 remote backend which is implemented in this repository.
Please do not close this ticket. It is a valid bug.
The text was updated successfully, but these errors were encountered: