4 ms·
None of this really applies to VPC (which is a private virtual network for only your own hosts and access is restricted lower down than at the ip layer). You ac
by stormbrew 11y ago
None of this really applies to VPC (which is a private virtual network for only your own hosts and access is restricted lower down than at the ip layer). You actually can have a public IPv6 address on AWS, it just has to go through ELB.
- teraflop 11y agoYou actually have it a bit backwards: you can only assign an IPv6 address to an ELB if it's not in a VPC. http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel... Crazy, right? Especially since new customers are forced to use VPC and don't even have the option of falling back to EC2-Classic.
- stormbrew 11y agoTo be clear, I was not saying that you can give an ELB in a VPC an IPv6 address. I was saying you can give a non-VPC ELB an IPv6 address. Basically I was pointing out that, however imperfect, Amazon has chosen to prioritize public access to IPv6 over private use of it.
- teraflop 11y agoAh, sorry for the misunderstanding then.
- falcolas 11y agoActually, it does apply, even in a VPC. The inability to tune TCP sockets affects your ability to scale certain services. It also makes routing within your VPC so much more entertaining to manage.