No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Not sure if related, but the new MAJOR release of the pulum-aws and underlying MAJOR release of the terraform provider cause a breaking change with authentication.

<https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade#changes-to-authentication>

When I'm using a old pulumi operator, (v1.9.0) it was working, but today it doesn't work, so I don't understand because the provider should be with the old method of authentication, no?

And I still no sure what should be changed in the code to make it works without providing any keys, only using assumed roles?

What version of the aws provider did you upgrade from -&gt; to ?

I didn't upgrade aws provider, just the operator then I rollback to the previous version, but I was still getting the same issue

Is there a way to specify the aws provider version in the Pulumi config file:
```encryptionsalt: KEY
config:
  aws:region: REGION```

I tried to go back to 5.13.0 but I still get the same issue

I found the solution, thank you for your help

For each resources, I'm adding the following: pulumi.ResourceOptions(version="5.17.0"). that version is the last one I tested where the auth was working