It would be a good start if AWS supported IPv6 on all their services in the first place. Everything enters through CloudFront so I don’t need any IPv4. But AWS’s own services don’t have IPv6 in every region, so I still have to provision NAT gateways.
Shdwdrgn@mander.xyz 9 months ago
Yikes. I get free IPv6 for my servers through Hurricane Electric since my ISP doesn’t provide it yet, I wonder if their service also works on AWS? I mean come on, if someone like Comcast can figure it out, why is it so hard for a major player like Amazon?
Max_P@lemmy.max-p.me 9 months ago
Lots of legacy networking I would assume.
Most services especially compute can get IPv6 so if all you have is EC2 instances you’re good. S3 is usually fine, but I think when you get into Lambdas and especially the more niche services, those are IPv4 only, so you need some IPv4 addressing.
Ironically I’ve really been enjoying the massive IPv6 address space, makes numbering dozens of VPCs and subnets a whole lot easier. I don’t get why it’s not in huge demand especially larger customers.
thejml@lemm.ee 9 months ago
It is actually in demand by one big customer, the DoD. Amazon is pushing hard to get all its services IPv6 by EOY as of this year’s re:Invent. Something like 98% need to be in place for DoD contracts.
And they’re trying to force people over to IPv6 by charging them per public IPv4 address, so, hopefully that spurs the migration. Larger address counts/space is super useful.