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

Hello,
Is it required or recommended to use a backend lock, like DynamoDB, when using an S3 backend?
If yes, how to configure it ?

The locks are in s3 bucket in /Locks , maybe locks in dynamodb are only for Terraform: <https://www.pulumi.com/docs/iac/concepts/state-and-backends/#aws-s3>

Yeh dynamodb locks are a terraform thing, pulumi treats s3 the same as any other file/blob store

<@U02J3T6A8LB> do you know if there are know issue with S3 backend and Automation API ?

Seems the automation api does not release the lock.
The lock is at the project or stack level ? its looks like the stack level, it is what I see in s3

at the stack level, and automation api shouldn't really have anything to do with it. Its the engine that locks/unlocks the file

I had forgotten to include the IAM permission `s3:DeleteObject`.
 It's working fine now.
 However, Pulumi fails silently when it can't delete the lock, this should raise an explicit error with the root cause.

I'd recommend opening up a GitHub issue with this finding. It should report the problem, not silently swallow things.