5 ms·
I've seen some VM providers charge more to get an instance with IPv4 connectivity. Amazon doesn't charge extra for that (last I looked anyway), so that's a pote
by toast0 6y ago
I've seen some VM providers charge more to get an instance with IPv4 connectivity. Amazon doesn't charge extra for that (last I looked anyway), so that's a potential advantage.
IPv6 penetration is growing, but Akamai reports that even the most IPv6 networks only go to ~ 92% IPv6. So if you want to have full reach, you need IPv4, but you don't really need IPv6 (although, you may want it, some of the CGNAT systems that users are behind are pretty bad, avoiding that is nice)
- shepherdjerred 6y agoAWS does charge for a dedicated (static) IPv4 address, but only when your EC2 instance is down. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-... https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/ https://aws.amazon.com/premiumsupport/knowledge-center/elast...
- nucleardog 6y agoFor anyone not as familiar with AWS, basically: * They'll provide a free dynamic IPv4 address attached to any interface/VM for the life of that VM. * They'll provide static IPv4 addresses. These are generally free, but you'll be charged if they're not attached to a VM (i.e., sitting unused). Only one IP per instance is free. Charge is a half cent an hour, so works out to about $3.65/mo to camp on an IP address.
- usr1106 6y agoNothing is free when you get it from a profitable business. EC2 prices are pretty high compared to other offerings if you run the machine permanently. The "free" IPv4 address is certainly a part of the price. (There are other parts like good maintenance, which you don't necessarily get from cheaper competitors) Scaleway charges you 1 € / month for such address whether you use it or not. That's a 25% premium on the cheapest machine when in use. Much cheaper than AWS whether in use or not. Not sure how many customers could perfectly live without the IPv4, but AWS seems to be in the market position to (covertly) charge them, too.
- im3w1l 6y agoDo users on cgnat typically have cgnat ipv6 or not?
- toast0 6y agoTypically not (but I guess it's possible). CGNAT is expensive to run, but carriers do it because it can be less expensive than getting more IPv4 addresses, and it's faster to add capacity than to get addresses. IPv6 addresses are very low cost and quick to ger assigned, so if you're supporting IPv6, and you run low on addresses, adding CGNAT doesn't make sense. It's much more typical to either have cgnat IPv4 and public IPv6, or just cgnat IPv4 and no IPv6 than to have cgnat both.
- maven29 6y agoIn the wake of the wannacry debacle, quite a few ISPs have moved IPv6 as well behind CGNAT.
- welterde 6y agoThat doesn't sound quite right to be honest - do you have a source for that? I don't even see what possible rational there could be for such a change. Most native v6 consumer already have firewalls for IPv6 in the CPE which block any incoming connections per default, so not even the misusing NAT as firewall argument applies here.
- topranks 6y agoNo there is basically no NAT with IPv6, apart from some very niche edge cases. NAT is expensive.