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

a coworker pointed out to me that, although the `aws.ec2.DefaultSecurityGroup` Pulumi documentation states:
```When the provider first begins managing the default security group, it immediately removes all ingress and egress rules in the Security Group. It then creates any rules specified in the configuration. This way only the rules specified in the configuration are created.```
it appears that default rules are not removed, even if some other rule has been supplied. <https://www.pulumi.com/registry/packages/aws/api-docs/ec2/defaultsecuritygroup/> is there a way to log the interaction with the api to see if there was some reason it failed to remove the rules? (maybe we have some security req I don't know about)