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

There aren't any other notifications attached to that bucket, right? Everything is in the code specified here related to the bucket? With it being intermittent, there's a couple possibilities, like an occasionally malformed ARN. The AWS classic provider is based off of the Terraform bridge, so it responds to using the `TF_LOG` environment variable to get it to dump some data while it's running. Here's the basic command I'll use:
```TF_LOG=TRACE pulumi up -v=11 --logtostderr 2&gt;&amp;1 | tee -a pulumi_log.txt```
The environment variable asks the classic provider to bubble up data. The end of the command tells Pulumi to share logs both to stdout/stderr and append them to a file called `pulumi_log.txt`. You could use that to get a bit more information and track down the oddity. Unfortunately, I don't see anything specific in your code that's raising a flag for me, so that's where I'd start.