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

Hmm that's a strange error. Just a thought but do you know what value `bucket.id` has? It's possible that the object lock configuration takes in the bucket name as the value for `bucket` and if `bucket.id` isn't the bucket name then that might explain the 400 BadRequest from AWS.

Ultimately I removed this block of code since it introduced a new bucket. I have an older untracked bucket that I'm using which produced from a previous setup, as a result of the retain_on_delete bucket parameter.