I have Jenkins running in a Windows server EC2 instance on a custom port. Firewall is open on that port, and security group's inbound rule matching it allowing any IP address (users can't sign up and anons can't even read).
Now I want to add an extra security layer, but if I remove that inbound rule in the security group and only allow that port to the vpn security group, I can't access Jenkins.
I'm currently restricting access to RDP using that same vpn security group and it works perfectly. What may be causing it?
I've already tried restarting Jenkins service, connecting and disconnecting to vpn and Jenkins url times out.
