-
Notifications
You must be signed in to change notification settings - Fork 135
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 AWS Single-Sign On (SSO) cached credentials when using AWS profiles #162
Comments
Happy to bump the aws client, however, an earlier bump was possibly responsible for the regression in #124. I'll bump the client and release a new version. |
I am thinking in trying different commits from 1.5.0 to 1.5.1 to see the exact commit that could have broken things for #124. |
That'd be great. That approach should work. Please let me know what you find! |
Problem commit was #119, looking deeper on it now... |
Thanks @michelzanini, let's continue the conversation on #124 to keep this issue focused on the AWS client. I've gone ahead and bumped the client version and released https://github.com/phillbaker/terraform-provider-elasticsearch/releases/tag/v1.5.5, I'm going to close this issue as presumably fixed. |
@phillbaker is there any configuration I need to set to use SSO? This is the error message I got while the same SSO setup works with other providers
|
Can you be more specific? What other providers work with this? According to the upstream docs (https://docs.aws.amazon.com/sdk-for-go/api/aws/session/#hdr-Shared_Config_Fields), the |
When using
aws_provider_profile
it is not possible at the moment to have this profiles using AWS SSO with~/.aws/config
file. This is fairly new on AWS CLI v2.Support for this has been added to Terraform 0.14.6+ (for s3 remote state) and on AWS provider (3.26+).
To support it, the only change is to bump AWS GO SDK to 1.37 or above.
Here is the PR that was done on AWS provider:
https://github.com/hashicorp/terraform-provider-aws/pull/17340/files
I believe if this same bump happens here it will work.
More info can be seen here hashicorp/terraform-provider-aws#10851 (comment).
Thanks.
The text was updated successfully, but these errors were encountered: