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

Nevermind. I figured it out. I just need to run `pulumi login` for each project at the path in the s3 bucket that I want, for example `pulumi login --cloud-url s3://&lt;s3-bucket-name&gt;/the/path/to/the/project/im/working/on`

That’s right.  See also <https://github.com/pulumi/pulumi/issues/2522|https://github.com/pulumi/pulumi/issues/2522> and <https://github.com/pulumi/pulumi/issues/2814|https://github.com/pulumi/pulumi/issues/2814>. 

<@UB3BGTV63> thanks for those links. I think I'm a little confused now. If I log into a different backend (even if it is within the same s3 bucket, just a different folder structure within it) then it doesn't sound like I can do a stack reference to a stack in another project, right? How can I setup the aws backend to have multiple projects with the ability to do stack references across projects?

I believe you have to log into the same backend across projects, and then use stack names that are unique across all projects - for example following a naming pattern of `&lt;project name&gt;-&lt;stackname&gt;`. 

Hmm.. I see. I wish it worked a little more like the Pulumi SAAS offering.

I can get this to work though. I'm already separating my environments into different git repositories, so I was already going to have 1 stack per pulumi project, so this should be ok to do (1 project, multiple stacks)

Right - the goal is that those two issues will be addressed so that this is easier. 