IPv6 Support for AWS Extended to 15 Regions
aws.amazon.com
aws.amazon.com
Unfortunately it looks like VPC ELBs are still IPv4 only. They have a link in the article from when they introduced IPv6 for non-VPC ELBs back in 2011. Are VPC ELBs being worked on anymore or are we going to have to move to Application Load Balancers for IPv6 support?
90s: We can inter network the world with IP!
00s: ISP's won't do SCTP, but TCP and UDP work fine
10s: eh gonna have to use https ...Edit: 24:30 is around the point he mentions it.
Is it just for the simplicity of your networking? One strategy is to define your IPv4 space inside one of your IPv6 networks such that you have dual addressing with directly mappable addresses.
Do you have some other use case than just simplicity of design?
That's how I tend to use AWS at the moment, with IPv4. Almost every resource (except AWS services) has a public IP assigned, few have open inbound security groups, most have open outbound security groups (but the option to restrict is handy).
Also, having instances connect to IPv6 parts of the internet while you can see which subnet of your vpc the traffic originates from, and maybe filter on that fact.
Having routable addresses is a different thing than them being public or private, which is determined by the fact if you accept traffic to them or not when it arrives at the last hop before entering your vpc.
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.
Sad.
Prior to that dhclient fix, dhcpv6 was basically unusuable on 16.04.
If you disable IPv4 entirely, then it's true that you won't be able to access the archive mirrors. However, this isn't exactly "out of the box". :)
If you do want to disable IPv4, then at the same time you'll also need to modify your /etc/apt/sources.list to point at archive.ubuntu.com (which does serve over IPv6).
We're looking at how we can best make the "no IPv4" case work with the in-cloud mirrors, and hope to have that resolved soon.
So I'm guessing that was the issue here.
If I wanted to deploy v6 in my home network I'd literally have to configure my EdgeRouter X on every VLAN in my home network (and as such stuff all IPv6 traffic on my network that crosses subnets into a single 1Gbe connection), since my TP-Link managed switch has no facility to put out a IPv6 RA (even though it supports IPv6 routing, go figure).
I'm really digging the age of vendor silicon where most switches just support whatever Broadcom/etc. put into their chips, but man I hope they catch up with IPv6 soon because right now only the big boys (Cisco/Juniper/HP/Dell/etc.) seem to have any hardware with full IPv6 support, and then you're paying a hefty price for the hardware + support contract (assuming you want software updates).
think about something like docker where each app may be running web/db/queues/mail/etc. with v6 each docker app/service could have its own ip so you can run on the default ports. you could even create a subnet per app to segment them off easily.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-mi...
1.) Allocate and associate an IPv6 block to the VPC.
2.) Configure internet gateway and routes in the VPC.
3.) Update security groups to include IPv6 in the VPC.
4.) Confirm current instance types support IPv6.
5.) Assign IPv6 address to instances.
6.) May require manual network setup on each instance if not using DHCPv6.
Amazon.com itself didn't move to AWS until VPC supported the bring your own address primitives. Not everyone can clean slate rewrite systems to bring them to the cloud, Amazon recognizing this is going to keep them dominating the market.
The problem is usually the $50 wireless access point most people bought 5 years ago doesn't pass ipv6 through.
Last time I checked (a few months ago), UVerse in Dallas didn't either.