hashicorp / hashicorp/packer

Support new AWS SSO sessions config

Open
#12,412 0 comments 26 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
15.8k
Forks
3.3k
PR merge metrics
PR metrics pending

Description

#### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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

#### Description

The AWS sdk supports a newer way to authenticate with SSO. The new method configures both a profile and a sso-session in ~/.aws/config. See here for more details: https://docs.aws.amazon.com/cli/latest/userguide/sso-configure-profile-token.html

When trying to run Packer with the newer SSO config, I receive the following error:
```
==> build.docker: Error fetching ECR credentials: no valid credential sources for found.
==> build.docker:
==> build.docker: Please see
==> build.docker: for more information about providing credentials.
==> build.docker:
==> build.docker: Error: SSOProviderInvalidToken: the SSO session has expired or is invalid
```

#### Use Case(s)

Using the newer aws sdk.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.