I’m not an AWS user, so the “Virtual Private Cloud” caveat confuses me. If I just click an EC2 instance, will that be in a “Virtual Private Cloud” or not? Also, are these IPv6 addresses publically reachable or not?
IPv6 Support for EC2 Instances in Virtual Private Clouds
81–90 of 114 posts
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#828 IPs per instance, max :/
This honestly doesn't surprise me. Adding an infinite number of IPs is one way bot writers get around rate limits. I've done it before when I worked for a company that made a facebook/myspace/etc crawler.
Infinite IP addresses aren't the same as infinite routable IP addresses. EC2 VPCs use private subnets, and instances created in VPCs don't have routable IP addresses unless you add them. It would be reasonable for AWS to allow infinite VPC subnet addresses to be attached to an instance, but only one or two public addresses.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#83I’m not an AWS user, so the “Virtual Private Cloud” caveat confuses me. If I just click an EC2 instance, will that be in a “Virtual Private Cloud” or not? Also, are these IPv6 addresses publically reachable or not?
They are public. When you create an AWS account, you will have a default VPC (this wasn't the case with the classic EC2), and when launching an instance, if you don't specify anything else, the instance you launch will be in the default VPC.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#84Pardon 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?
> Is there hardware out there on the public internet that cannot communicate over ipv4 already?
Well there better not be because we're totally not ready because of shit like this. That's why it's needed.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#85Is there a succinct developer/administrators guide to IPv6? I recently discovered my home IP is ipv6 and have started to realize that it is more than just a larger address range. e.g. arp is replaced with ndp. While I haven't yet found a guide that has more depth than the very basics, but isn't a full on Cisco manual.
I tried writing one a few years ago when I got IPv6 at home:
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#86I find it interesting that this didn't make into the keynote. Is the actual interest really low?
I went to one of the first IPv6 sessions at re:Invent this morning. The room was for maybe, 300-400 people? There were 40 or so people in it. So, yes, the interest is low. That said, I think it's a great signal to the industry, and I'm excited to try to use IPv6!
> The room was for maybe, 300-400 people? There were 40 or so people in it. So, yes, the interest is low.
I think everyone who needs IPv6 is just not using AWS (anymore).
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#87[deleted]
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#88Earlier quoted context omitted.
In 2017, one should instead ask why it wouldn't be.
Because there are many other factors in choosing a hosting provider (price, performance, features, security, scalability, etc). It seems a bit weird that all of these would be less important to someone than IPv6. Though I guess I can imagine that for some businesses it could be hugely important. Was just wondering what OPs business was that it became an overriding priority.
Rolling out an IPv4 only stack right now is debt. IPv6 has finally hit the point where there's no longer an if portion to the question, but rather a when. Every server rolled out in an IPv4 only setup, every service built, etc, is one more potentially service-interrupting area that will have to be changed when port your stack to IPv6. If you're young and small, starting as IPv6 native means that the next few years you'll have an advantage over your competitors because they'll be thinking migrations while you're thinking about growing your business.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#89Earlier 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?
A few months ago Apple made it a requirement for all new iOS apps and app updates to support IPv6 only networking.
If the app backend is not also available from a network where IPv4 is completely blocked, the app is rejected.
At the same time, AWS does not let new accounts to create EC2 instances outside of VPC, and only provided IPv6 support in the non-VPC classic stack (only available to old AWS accounts that signed up years ago).
So for the last few months, AWS has been unusable as a backend for iOS apps unless you have an old classic AWS account.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#90Earlier quoted context omitted.
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?
A few months ago Apple made it a requirement for all new iOS apps and app updates to support IPv6 only networking. If the app backend is not also available from a network where IPv4 is completely blocked, the app is rejected. At the same time, AWS does not let new accounts to create EC2 instances outside of VPC, and only provided IPv6 support in the non-VPC classic stack (only available to old AWS accounts that signe…
api.twitter.com doesn't haven an IPv6 address and yet twitter continues to function on my iPhone.
I don't think your description of Apple's requirement is accurate.