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

Yes, you would use Stack Outputs from the _infra_ stack, and referenced from the application stack.

This is a good choice for anything shared, eg VPCs ( including Subnets, etc ).

We typically don't use Pulumi directly for this, but rather put these id's in SSM Parameters, and use that for lookups.

thanks a lot for your response, this is very helpful!

I was hoping to start with a single repo/project for a while, but then was forced into this pattern (ECS definition includes container version; to update container version for a deploy, have to run Pulumi; therefore Pulumi has to be in the app's repo for CI)

Useful reading:
• <https://www.pulumi.com/docs/guides/organizing-projects-stacks/|https://www.pulumi.com/docs/guides/organizing-projects-stacks/>
• <https://www.pulumi.com/blog/organizational-patterns-infra-repo/|https://www.pulumi.com/blog/organizational-patterns-infra-repo/>