From 4ecc685f398c1e94d9605f435284060bd9dfcec8 Mon Sep 17 00:00:00 2001 From: Tomasz Cholewa Date: Tue, 1 Aug 2017 01:04:17 +0200 Subject: [PATCH] Updated info regarding ALB Host header support (#468) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b527952..1029d4b 100644 --- a/README.md +++ b/README.md @@ -1054,7 +1054,7 @@ ALB - 🔸ALBs only support HTTP/2 over HTTPS (no plain-text HTTP/2). - 🔸ALBs only support HTTP/2 to external clients and not to internal resources (instances/containers). - ALBs support HTTP routing but not port-based TCP routing. -- ALBs do not (yet) support routing based on HTTP “Host” header or HTTP verb. +- ALBs support routing based on HTTP “Host” header or HTTP verb - 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.