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

The workarounds are
1. to comment out the code, deploy, comment it back in, redeploy, or
2. to migrate the awsx code to aws code and use the SecurityGroup and SecurityGroupRule classes directly.

Is this expected? Is it a bug? Maybe I'm using the `createIngressRule()` methods incorrectly?

Sounds like a bug, but is it possible you're creating the same rule with overlapping cidr blocks? I seem to recall I've run into that in the bast and the error message from AWS wasn't immediately obvious that was the issue.