You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FWIW, AWS suggest 127.0.0.1/32 when you need to limit egress on security groups defined in CloudFormation. If, for whatever reason, AWS were to allow broadcast traffic in a VPC, 255.255.255.255/32 would match it. Where as the loopback netblock should never be seen outside of the loopback device.
I created a pull request that fixes this issue. It restricts all inbound SSH rules to only the creator's IP Address at the /32 range. Should web access on port 8080 be restricted as well? That's an easy change.
Restrict access to a non-existent IP Address by default and require the user to enter their /32 IP as a parameter.
The text was updated successfully, but these errors were encountered: