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 want to understand the behaviour of pulumi

• when I run `pulumi up` for the first time, it created everything successfully
• if I rerun `pulumi up` it throws error saying entity already exists
• in aws cloudformation it just says that no changes required
• is there a way we can do `pulumi up` multiple times without failing

What resources are deployed. Many resources need redeployment even with no updates (this is how the underlying terraform providers worked). Example if an instance uses the inline sgs in aws.

what provider version and are you using pulumi cloud ?

The only way this would happen would be if you are changing the Pulumi name of the bucket without changing its S3 name. Pulumi uses a desired state model: `pulumi up` doesn't simply create the resources, it does whatever's needed to get the in-cloud resources matching the in-code shape of the resources. So it will update, delete, replace or whatever. It should always be safe to run `pulumi up`, unless there's something "unsafe" in the code.