8 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.
IPv6 Support for EC2 Instances in Virtual Private Clouds
11–20 of 114 posts
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#12I 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).
The biggest advantage I see (which is heavily coloured by the use cases I faced at Heroku on the Add-ons team) is being able to peer many VPCs without gymnastics to avoid IP range clashes and routing issues. I haven't looked at AWS' IVv6 announcement in enough detail to know if it addresses this head on, but I always looked forward to IPv6 as an avenue to making that kind of work much more straight forward.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#138 IPs per instance, max :/
[deleted]
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#14Earlier quoted context omitted.
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).
The biggest advantage I see (which is heavily coloured by the use cases I faced at Heroku on the Add-ons team) is being able to peer many VPCs without gymnastics to avoid IP range clashes and routing issues. I haven't looked at AWS' IVv6 announcement in enough detail to know if it addresses this head on, but I always looked forward to IPv6 as an avenue to making that kind of work much more straight forward.
But if the peering limit is still 50 vpcs - I guess it might help if/when inter-region peering ships
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#15Earlier quoted context omitted.
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).
VPC ELBs and ALBs don't support ipv6 though. Presumably this is the first step to adding that support, although it's still not available even in the new ipv6 VPCs.
They just announced during the ELB session that ALBs will be supporting full IPv6 also.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#16I 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).
The opposite direction is more interesting.
It might be finally possible to reach things floating out there on the internet which have an IPv6 address.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#17Finally! It's been a major deficiency in AWS. Can't wait to see this roll out to us-west-2.
Do they have an official roll-out schedule yet?
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#188 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.
Out of curiosity, why does Amazon consider it their responsibility to prevent that? I'm personally glad that they do, but bots use resources, which is good for Amazon (money in their pocket), and as far as I know Amazon doesn't have anything it wants to protect from bots (at least, anything that would be heavily limited by IP).
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#19Earlier quoted context omitted.
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.
Out of curiosity, why does Amazon consider it their responsibility to prevent that? I'm personally glad that they do, but bots use resources, which is good for Amazon (money in their pocket), and as far as I know Amazon doesn't have anything it wants to protect from bots (at least, anything that would be heavily limited by IP).
Well, one explanation might be the reputation of their IP ranges. Already, payment processors and some mail servers will give extra scrutiny to IP ranges belonging to AWS. If AWS is made attractive to that audience and damage is done to the reputation (in various systems) of those IP ranges, their offering becomes less compelling to all customer demographics.
Re: IPv6 Support for EC2 Instances in Virtual Private Clouds
#20Finally! It's been a major deficiency in AWS. Can't wait to see this roll out to us-west-2.
s/AWS/everywhere but Google/