31–40 of 114 posts
I find it interesting that this didn't make into the keynote. Is the actual interest really low?
Most production environments terminate on Cloudfront endpoints (or other CDNs) or ELBs/ALBs; not much need for IPv6 to individual instances (which can use IPv4 internally).
8 IPs per instance, max :/
Might be a dumb question, but why would you want or need more than one IP address for an instance? It's not like more addresses will let you download/upload things faster. Maybe if you want to run multiple web servers on port 80 and give each one a different IP address, but how often do people do that, especially more than 8 times over?
Finally! It's been a major deficiency in AWS. Can't wait to see this roll out to us-west-2.
This is one of those that's more of a "about damn time," features that'd I'd care about if I already didn't go with Digital Ocean/Linode instead just because of IPv6 support.
Finally! It's been a major deficiency in AWS. Can't wait to see this roll out to us-west-2.
I'm kinda sick of all the AWS posts on here, but I'm trying to be fair since some of them are really interesting. This is one of those that's more of a "about damn time," features that'd I'd care about if I already didn't go with Digital Ocean/Linode instead just because of IPv6 support.
Earlier quoted context omitted.
I'm kinda sick of all the AWS posts on here, but I'm trying to be fair since some of them are really interesting. This is one of those that's more of a "about damn time," features that'd I'd care about if I already didn't go with Digital Ocean/Linode instead just because of IPv6 support.
Just curious but why is IPv6 support such a priority for you that it would be the deciding factor in your choice of hosting provider?
Finally! It's been a major deficiency in AWS. Can't wait to see this roll out to us-west-2.
I'm kinda sick of all the AWS posts on here, but I'm trying to be fair since some of them are really interesting. This is one of those that's more of a "about damn time," features that'd I'd care about if I already didn't go with Digital Ocean/Linode instead just because of IPv6 support.
As long as AWS is both widely used by existing users, and is a likely option for new users evaluating alternatives, these AWS posts are always relevant on HN.
Pardon my ignorance, but why is this needed? I've seen dozens of "+1s" for ipv6 on both AWS and GCP, but no one says why really. Is there hardware out there on the public internet that cannot communicate over ipv4 already?
You can argue that behind NAT there is still IPv4 connectivity with public internet, but it is actually closer to proxying (i.e. having some device talk to internet on your behalf) than to routing (i.e. have some device pass your packets on).
Long story short, there is (for a long time already), no IPv4 public internet. There is IPv4 public interconnect between millions of isolated IPv4 islands. And a lot of hacks and shady engineering to make packets traverse from interconnect to islands and back.