From d9e9cc133ea341ad449d9957a5cf5e8cb3208982 Mon Sep 17 00:00:00 2001 From: Laurent Jalbert-Simard Date: Thu, 23 Feb 2017 23:00:25 -0500 Subject: [PATCH] Update ALB Tips and Gotchas regarding ipv6 (#384) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7762bd3..1241075 100644 --- a/README.md +++ b/README.md @@ -1025,6 +1025,7 @@ ALB - šŸ“’ [Homepage](https://aws.amazon.com/elasticloadbalancing/applicationloadbalancer/) āˆ™ [User guide](https://aws.amazon.com/elasticloadbalancing/applicationloadbalancer/developer-resources/) āˆ™ [FAQ](https://aws.amazon.com/elasticloadbalancing/applicationloadbalancer/faqs/) āˆ™ [Pricing](https://aws.amazon.com/elasticloadbalancing/applicationloadbalancer/pricing/) - šŸ„**Websockets and HTTP/2** are [now supported](https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/). +- šŸ„**Internet Protocol Version 6 (IPv6)** is [now supported](https://aws.amazon.com/about-aws/whats-new/2017/01/announcing-internet-protocol-version-6-ipv6-support-for-elastic-load-balancing-in-amazon-virtual-private-cloud-vpc/). - Prior to the Application Load Balancer, you were advised to use TCP instead of HTTP as the protocol to make it work (as described [here](http://www.quora.com/When-will-Amazon-ELB-offer-SPDY-support)) and use [the obscure but useful Proxy Protocol](http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/enable-proxy-protocol.html) ([more on this](https://chrislea.com/2014/03/20/using-proxy-protocol-nginx/)) to pass client IPs over a TCP load balancer. ### ALB Tips @@ -1041,7 +1042,6 @@ ALB - Instances in the ALBā€™s target groups have to either have a single, fixed healthcheck port (ā€œEC2 instanceā€-level healthcheck) or the healthcheck port for a target has to be the same as its application port (ā€œApplication instanceā€-level healthcheck) - you can't configure a per-target healthcheck port that is different than the application port. - ALBs are VPC-only (they are not available in EC2 Classic) - In a target group, if there is no healthy target, all requests are routed to all targets. For example, if you point a listener at a target group containing a single service that has a long initialization phase (during which the health checks would fail), requests will reach the service while it is still starting up. -- As of December 2016, although it has been announced as coming soon, ALBs [do not yet support IPv6](https://aws.amazon.com/about-aws/whats-new/2016/12/announcing-internet-protocol-version-6-support-for-ec2-instances-in-amazon-virtual-private-cloud/). Even if the ALB is launched in an IPv6-enabled VPC and subnet, it will only have IPv4 addressing. Elastic IPs -----------