Oddbean new post about login | logout I don't understand when you say your isp doesn't support port forwarding. You get an IP from your isp and you can open whatever ports you want, and if you use ddns you don't even need a public IP. Where would forwarding be involved? Am I missing something from your predicament?
I think wire guard is a good idea rather than open up the actual ports to your server to the internet, but even then I don't get why you mention aws. How come you can't just terminate wireguard on a pi or router at home and have that as the only port open on your fw?
I am behind a Double-NAT. My ISP doesn't give me just 1 IP because it's dynamic. In order to expose my local machine to the internet, I am trying to host wireguard on aws and forward the ports there. Then I would connect my local machine to the wireguard.
I didn't even know this was a thing, but it makes sense. It's like someone setting up another router on your home network and putting you behind that. You can only make outbound connections. I'd prioritise a better ISP but in lieu of that the tunneling back in over the outbound connection makes sense.