5 ms·
Honestly, you'd do better scripting the aws cli to update the sec group with your IP address, which is how we've handled WfH for server SSH/plesk/SQL access. I
by tehbeard 5y ago
Honestly, you'd do better scripting the aws cli to update the sec group with your IP address, which is how we've handled WfH for server SSH/plesk/SQL access.
It's like half a dozen lines of bash, I'll see if I've got it on my home pc.
- noduerme 5y agoThat's a cool idea! Never dawned on me to do that.
- LilBytes 5y agoSSM Port Forwarding and Tailscale are your friend. I'm using a mixture of both with most staff WFH now and their home IP addresses not being static. Tailscale especially is an amazing product though I've only had it running at work and home for around a month. All that said, a simple script as you pointed out is also great :)
- bombcar 5y agoWhat’s fun is when those IPs remain in the rulesets even after they’re no longer used or needed - and the residential DHCP changes and now someone else has a direct line. Or it points to an AWS IP that eventually gets handed back and recycled …
- tehbeard 5y agoAnd that's where you both implement and act on security policies to mitigate and avoid this based on the threat model you're up against.