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

It seems like what's happening is the cloudwatch log group I define is being created and from the pulumi output it looks like it's a dependency of the lambda created from the `callbackFunction` call. However, when the lambda is actually deployed, a default cloudwatch log group is being used instead. This one is not tracked in the stack and cannot be destroyed using pulumi.

Not sure if i'm maybe just missing some config somewhere, but this behavior seems odd.

nvm resolved. Didn't realize for lambdas the function name has to match the cloudwatch name and that you couldn't assign a custom one with a different name.