2 ms·

Half[0] of AWS's services don't work with IPv6, despite Amazon charging extortionate rents on IPv4 addresses. So... yeah, for that reason I do need to keep usi

by M2Ys4U 3y ago

Half[0] of AWS's services don't work with IPv6, despite Amazon charging extortionate rents on IPv4 addresses. So... yeah, for that reason I do need to keep using IPv4, at least until either 1) AWS gets its act together; or 2) my employer moves away from AWS (which is very unlikely). [0] Hyperbole... but probably not that unrealistic.

db48x 3y ago
Yea, the AWS situation is pretty dumb. We know full well that under the hood, every component that Amazon uses to build those services supports IPv6. When you star using some AWS service, it starts up a fleet of compute instances behind the scenes to handle the traffic you’re going to send it. If the developer of the service remembered to check the “IPv6” checkbox for those instances then the service will support IPv6, otherwise it won't. But as the article points out, it doesn't really matter. You could run a NAT64 service of your own, inside the VPC that AWS gives you. Your own systems can then be IPv6–only, saving you money while still using AWS services that still don't support IPv6.