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
terraform-aws-provider v3.26.0+: aws-go-sdk v1.37.0+ causes Terraform to fail reading credentials from environment if SSO configuration in ~/.aws/config is incomplete
#17370
Closed
christophetd opened this issue
Feb 1, 2021
· 5 comments
· Fixed by #17469
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform CLI and Terraform AWS Provider Version
Terraform v0.14.5
Terraform AWS provider v3.26.0. Confirmed this bug does not occur on v3.25.0
ewbankkit
added
provider
Pertains to the provider itself, rather than any interaction with AWS.
upstream
Addresses functionality related to the cloud provider.
and removed
service/iam
Issues and PRs that pertain to the iam service.
labels
Feb 1, 2021
This was confirmed in aws/aws-sdk-go#3768 to be an aws-go-sdk issue which will be fixed in their next release. I suggest we wait until the fix is released on their side, then I guess the next release of terraform-provider-aws will solve the issue?
See also: aws/aws-sdk-go#3768
Community Note
Terraform CLI and Terraform AWS Provider Version
Configuration Files
Terraform configuration file:
~/.aws/config
:Description
Authentication. With the configuration described above, using aws-vault / the AWS CLI, I'm authenticating using AWS SSO:
Expected behavior: When running
terraform apply
, the credentials from my environment are used to authenticate against AWSActual behavior:
Note that adding random sso_account_id and sso_role_name to
~/.aws/config
does allow to work through this bug, e.g.References
aws/aws-sdk-go#3768
The text was updated successfully, but these errors were encountered: