Question

A cloud engineer adds an inbound rule to a security group to allow HTTPS (443) from a partner's IP range. Testing from the partner network still fails to reach the application, while access from the corporate office (also allowed) works fine. The engineer confirms the rule shows correctly in the console and the application is listening on 443. Following a structured troubleshooting methodology, what is the MOST likely next step to identify the cause?

Accepted Answer

Verify the partner's actual public (NAT/egress) source IP matches the CIDR entered in the rule using connection or flow logs

Answer

Restart the application service so it picks up the new firewall rule

Answer

Increase the security group rule limit because the group has reached its maximum entries

Answer

Add a matching outbound rule to the security group to permit the return traffic