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

All resources accept CustomResourceOptions <https://www.pulumi.com/docs/intro/concepts/resources/options/|https://www.pulumi.com/docs/intro/concepts/resources/options/> which accept Provider such as <https://www.pulumi.com/registry/packages/aws/api-docs/provider/|https://www.pulumi.com/registry/packages/aws/api-docs/provider/> with which, in turn, you can specify an AWS profile for API calls. Technically that’s all you need, very flexible... but too verbose, though.
Instead you may want to group resources belonging to the same account as a Pulumi stack and do `pulumi config set aws:profile` <https://www.pulumi.com/registry/packages/aws/installation-configuration/#set-up-multiple-profiles|https://www.pulumi.com/registry/packages/aws/installation-configuration/#set-up-multiple-profiles> per stack. I have a cross-regional (but not cross-account) setup consisting of multiple stacks.
I’d be interested in learning how others organize complex Pulumi AWS projects

merp sorry totally forgot I posted this, I thiink I’m on the right track right now with my setup, I have separate stacks already setup with Organization -&gt; OU -&gt; Account, and specify Account-level permissions separately in each config respectively