https://pulumi.com logo
#aws
Title
# aws
f

fast-flower-40813

11/14/2022, 7:18 PM
Hi everyone, I'm having issue using vpc peer connection ( it was working like 3 weeks ago but it stops working) when assuming role. I think it's due to the upgrade of the terraform aws provider: https://github.com/pulumi/pulumi-aws/issues/2214... Does anyone have the same issue? Thank you
m

millions-furniture-75402

11/14/2022, 7:22 PM
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.
f

fast-flower-40813

11/14/2022, 7:30 PM
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?
m

millions-furniture-75402

11/14/2022, 7:33 PM
What version of the aws provider did you upgrade from -> to ?
f

fast-flower-40813

11/14/2022, 7:35 PM
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:
Copy code
encryptionsalt: KEY
config:
  aws:region: REGION
if so, what version, should I use?
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
m

millions-furniture-75402

11/15/2022, 6:29 PM
What was the solution?
f

fast-flower-40813

11/15/2022, 6:34 PM
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