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

Untitled.ts

I need to provision AWS resources in multiple regions. Locally I'm using a local EC2 instance metadata service agent (called <https://github.com/otm/limes|limes>), this since we have a multi-account setup where we need to assume roles. However, with this setup of two providers the region doesn't seem to take affect. Using the `providerAwsGlobal`  provider still creates resources in "eu-west-1". The instance metadata service is on a profile that defaults to "eu-west-1", but it's still possible using it to interact with other regions. E.g. if I run `AWS_REGION=us-east-1 aws ...` it nicely interacts with another region.

Anyone encountered this and have any ideas how to tackle it? Does pulumi support setting region when the instance metadata service is relied upon for authentication?

_EDIT: I noticed, having a resource outside my ComponentResource it creates it in the correct region. But not the resources within the ComponentResource. I updated the code example for more clarity_

Yeah, it's within the ComponentResource it's not working. Creating the resource outside with a reference to the same provider, works. :thinking_face:

Can resources within a ComponentResource only be connected to one and the same provider?