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

&lt;glib&gt;Look for user access to cloud services&lt;/glib&gt;

You can try `pulumi refresh`: it's a manual process, and it will find non-drift changes too, but it can work.

You can also run `pulumi up` on a schedule, to continually revert drift; then listen for the screams. (No, honestly, I'm serious. It works.)

And there's your service provider's own logs (CloudWatch or similar). Any changes by non-Pulumi roles/users are a lead to follow.