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

Are the connection and accepter set up in the same project? You'll have to run it at least twice to get this to work. I would recommend separate projects or an autoamtion-api wrapper for this sort of work, since you need to have the two resources updated in a specific order.

VPC peering is very awkward to set up through IaC. Some of the alternatives (like gateway endpoints, privatelink, and there's at least one more service that I can't remember right now) can help you avoid VPC peering.

Thank you, i had no idea autoamtion-api was thing :slightly_smiling_face:

You need to reproduce the console functionality of
1. creating the connection; then after it is created
2. accepting the connection.
In Pulumi, you probably need to `up` or `refresh` in the first account too, so that Pulumi knows about the new connect state. I'm not certain about that though.

Do i need to create 2 peering for peering 2 regions?


US &lt;===&gt; EU

yes, thats i meant to say :slightly_smiling_face:

You need 1 peering between 2 VPCs. One connection is bidirectional.

This is independent of AZs, regions, accounts, anything.