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

For storing state file of my pulumi stack I am using s3 bucket. Should I use single s3 bucket for all stacks/env? or should I create 3 different buckets for state file of 3 different stacks?

Which is better/preferred?  Our aim it to keep state file of different env as isolated as possible.

Please suggest.

Now that you can get Pulumi to lock state during deployments, it is best to use one URL for all projects that are able to access each other via StackReference.

There is a risk of collision when two projects share a single unlocked backend (S3 bucket URL), but that's mitigated by Pulumi's locking.

And you cannot use StackReferences between projects with different backend URLs.

thanks <@U012UJTT55M>, We have decided to go with different bucket for different stack/env