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
Yep, this is a known issue - there was an attempt to fix it not so long ago over in #796, but it turns out to be more complex. I'd welcome a PR if anyone has the time to address it.
Just a note for other readers, same bug as #521. That one has a more complete description of the problem, that it involves profiles configured in ~/.aws/config with a region
Environment
Erlang/OTP 24 [erts-12.0.4] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit]
Elixir 1.12.2 (compiled with Erlang/OTP 24)
ExAws version
mix deps |grep ex_aws
ex_aws 2.2.6 (Hex package) (mix)
locked at 2.2.6 (ex_aws) c22ce2b8
ex_aws_kinesis (Hex package) (mix)
locked at 2.0.1 (ex_aws_kinesis) 7ba0e467
ex_aws_s3 2.3.0 (Hex package) (mix)
locked at 2.3.0 (ex_aws_s3) 0b13b114
HTTP client version. IE for hackney do
mix deps | grep hackney
hackney 1.18.0 (Hex package) (rebar3)
locked at 1.18.0 (hackney) 9afcda62
Current behavior
Given config:
And Config creation:
I would expect a Config like:
Expected behavior
In fact, the config created is:
This prevents successful actions against S3 resources in non-us-east-2 regions.
The text was updated successfully, but these errors were encountered: