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

I'm considering a Pulumi backend strategy. I want to host all created IaaC on S3 using `PULUMI_BACKEND_URL=<s3://pulumi>`, and I'm wondering whether to create a single bucket for all projects or use `<s3://pulumi/project-name>`, where each project has its own directory. Alternatively, I could create a separate bucket for each project, like `<s3://pulumi-project-name>`.
I'd love to know how you've approached this in your solutions!

If you want the projects to be able to share stack references, then they'll need to be in the same bucket path.

the CLI will automatically make a folder per project anyway

so just set the backend url to the top level <s3://pulumi>