This message was deleted.

hey there! I'm not really following here, this seems to be expected behaviour. If you create a security group it should still be created, but you haven't fully populated the rule, so no egress rules apply

This is likely a downside of the embedded-security-rule sugar. What happens if you do the equivalent without the

egress

property and with a

SecurityGroupRule

instead? I think it'll probably fail at compile time. Which is, imo, another good reason to avoid sugar constructs like this and stick with objects that map directly to resources.