- cross-posted to:
- service_clouds@lemmy.ca
- hackernews@derp.foo
- technews@radiation.party
Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead.
The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. … These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said.
If my ISP doesn’t support IPv6, would I need a proxy or something to access an AWS instance with only an IPv6 address?
A tunnel. I’ve used these before https://tunnelbroker.net/ and https://www.sixxs.net/main/ probably 10 years ago now. They were pretty good. But of course you need something to act as a router on your network for it to set it up for the whole network. A raspberry pi would be enough or anything running linux. Of course you can probably just set it up on one machine too. I’ve never done that though.
You could use an IPv6 tunnel broker service. I know Hurricane Electric offers a service free of charge. I use it and it’s not bad. Hurricane Electric also has an IPv6 tutorial. See (https://www.he.net)
I’ve tried using Hurricane Electric’s tunnels on pfsense but it just kills my internet connection and the only solution is to reboot
It is very area dependent and what path your data takes. It just so happens that the pathway that my data takes to reach Hurricane Electric’s server in NYC is really optimal. I have latency comparable to a native IPv6 network. It’s certainly better than my ISP, Verizon’s, native IPv6 in my area where my data goes to Virginia and then back to NYC.