AWS IPv6 Information Hub
Welcome, packet pilgrim!
Introduction
The world is finally moving on from IPv4. AWS has started charging for public IPv4 addresses years ago, arguing it would be "accelerating your adoption of IPv6".
Around 50% of all clients globally now have IPv6 connectivity. In many countries, IPv6 actually reduces latency for end users! (Google IPv6 statistics)
Many governments now have mandated deadlines for IPv6 support in their systems, with some governments even setting an end date for IPv4 support.
IPv4 usually requires NAT, and AWS Managed NAT Gateway's per-gigabyte traffic charges can be an absurdly high line item.
IPv6 brings serious savings, better performance, has no more NAT, no more subnet sizing guesswork, no more address collisions.
This site provides up-to-date technical information to get you started with IPv6 on AWS.
Topics
Service API Endpoints
Years ago, this site started as single page providing detailed data on IPv6 support for public AWS service API endpoints. A modernized version of the original full endpoints matrix is available here, in addition to a new summary page for those endpoints.
Other Topics
This page is work in progress. The sections mentioned below are stubs for now and will be filled with content soon™.
IPv6 Connectivity
You will find information on ingress traffic -- that is, allowing IPv6 clients to connect to your services ...
There is information on egress traffic -- allowing your AWS resources to connect to AWS and third-party services like Docker Hub using IPv6 (reducing NAT Gateway traffic!).
AWS SDKs
An introduction to using the AWS SDKs with IPv6, which isn't as straight-forward as you'd expect.
Audience
The information on this site assumes familiarity with IPv6 in general. If you are not familiar with IPv6, check out book6, "a practical introduction to IPv6 for technical people".