did the aws stuff change so that creating a provider no long

Question

did the aws stuff change so that creating a provider no longer uses the like default stuff i now get this error when trying to create a provider in another region ```providerCredentialOpts and an AWS provider instance must be set together``` i very much want to not configure the auth options for the provider just like is the case for the default aws provider

billowy-army-68599 · Answer

hey i think you re getting this from the EKS provider right

billowy-army-68599 · Answer

or is it the pure aws provider

bitter-dentist-28132 · Answer

hard to say but it s possible ``` Error providerCredentialOpts and an AWS provider instance must be set together at new Cluster home chuck le codes test asp pulumi front node modules pulumi cluster ts 1382 19 ```

billowy-army-68599 · Answer

yeah it s from the EKS provider can you share your code are you using the `AWS PROFILE` environment variable

bitter-dentist-28132 · Answer

i can but it s a lot of code i am not using `AWS PROFILE` because i am using the `default` profile

bitter-dentist-28132 · Answer

with `TF LOG=trace` i can see i am getting 403 errors from sts which doesn t really make sense

bitter-dentist-28132 · Answer

ah i see i was using a different profile before and that s baked into the state file

bitter-dentist-28132 · Answer

that s likely it

bitter-dentist-28132 · Answer

yeah that seems to be the issue thanks for pointing me in the right direction

bitter-dentist-28132 · Answer

well i still have that issue on newer versions but it works with older versions good enough for me