-
Notifications
You must be signed in to change notification settings - Fork 530
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
With sso-session config "Required key: :secret_access_key must be a string, but instead is..." #951
Comments
fwiw, terraform has a similar limitation: hashicorp/terraform-provider-aws#28263 |
Okay, took me a while to pin down, because that's a super misleading error message (and I'm just adding some code to improve it now). But yes, the upshot is that nobody has written code to support that style of auth config. PRs welcome :) Thanks for the detailed report. |
Incidentally, if you're looking to add support, the place to do it is |
This comment was marked as outdated.
This comment was marked as outdated.
Ah my previous comment was somewhat off. As @chrismo wrote,
So I can confirm that the problem is, ex_aws's awscli config provider not yet supporting newer aws sso config structure (sso-session). |
For the time being, I'm going to revert my sso config to legacy structure as a workaround. |
I think this issue will be fixed by #1080 |
Environment
mix deps |grep ex_aws
mix deps | grep hackney
Current behavior
Using the newer sso-session config which supports automatic token refresh.
~/.aws/config
runtime.exs
iex
Expected behavior
Expected behavior is that the request would succeed. If the configuration changes back to the legacy config, then the request works.
~/.aws/config
iex
The text was updated successfully, but these errors were encountered: