Unless something has changed since I just happened to have checked earlier today, VPC ELBs are still IPv4-only. They return AAAA records on the ipv6 and dualstack subdomains like their classic/non-VPC counterparts (which do fully support IPv6), but the ports aren't open on the returned addresses, so it's not very useful. Maybe someone from Amazon can chime in?
This is great news. The reason we support IPv6 lookups but only over IPv4 connections on <a href="https://ipinfo.io" rel="nofollow">https://ipinfo.io</a> is because we use AWS with VPC, which hasn't historically supported IPv6. Except many sites/services to add IPv6 now that were previously limited by this.
Fun fact: Ubuntu 16.04 image offered on Amazon does not support IPv6 out of the box.<p>Even when you log in via ipv4, and make relevant networking changes (basically enabled DHCP for v6), it will still fail to apt-get update, because eu-central-1.ec2.archive.ubuntu.com is ipv4-only.<p>Sad.
Hypothetically speaking, does anyone know if enabling IPv6 on a small VPC using 100% of its IPv4 addresses would allow you to spin up additional EC2 instances assigned IPv6 addresses?