-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support sso-session #2272
Comments
This is tracked in hashicorp/terraform-provider-aws#28263 in the upstream provider. |
The easiest way to work around this is to grab temporary credentials from the SSO session. https://github.com/jaxxstorm/aws-sso-creds allows you to do this easily |
As a workaround I'm able to use If you are using Pulumi to manage multiple accounts at once, create a profile for each account, specifying its account ID and then specify that account's profile in the provider. You will need to use
|
We are already doing what @Fydon suggested but I am keen to use the new feature for SSO once Pulumi and some other tools support it. |
I faced this issue |
The Terraform Provider AWS issue mentioned above has been resolved so I assume that it should be possible to resolve in Pulumi now as well. This has potentially been resolved in AWS Native provider already. |
I think that this is now working with the configuration below. If you have multiple AWS accounts, you still need a profile for each account. However you only need to login once to the sso-session when everything is configured:
|
I can confirm that this seems to be working now. |
Indeed, this should have shipped in 6.0 of the provider, so it's great to hear folks are finding success with it. Marking as resolved. |
Hello!
Issue details
AWS SSO now supports configuring an sso-session which can be used to derive profiles without repeating values. As an example:
However, the Pulumi CLI doesn't appear to honour these values
The text was updated successfully, but these errors were encountered: