From 59c57464725dd013dea35a2b0c332bee5b96fb27 Mon Sep 17 00:00:00 2001 From: Dan O'Brien Date: Sun, 8 Oct 2017 09:03:56 -0400 Subject: [PATCH] make NLBS NLBs --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 57bc830..f9f7985 100644 --- a/README.md +++ b/README.md @@ -1028,7 +1028,7 @@ Load Balancers - CLBs and ALBs can optionally handle termination for a single SSL certificate. - All can optionally perform active health checks of instances and remove them from the destination pool if they become unhealthy. - CLBs don't support complex / rule-based routing. ALBs support a (currently small) set of rule-based routing features. NLBs have most extensive routing options. -- CLBs can only forward traffic to a single globally configured port on destination instances, while ALBs can forward to ports that are configured on a per-instance basis, better supporting routing to services on shared clusters with dynamic port assignment (like ECS or Mesos). NLBS support multiple ports on same IP; registering targets by IP address, including targets outside the VPC for the load balancer; ECS can select unused port for scheduling a task then register a target group using this port. +- CLBs can only forward traffic to a single globally configured port on destination instances, while ALBs can forward to ports that are configured on a per-instance basis, better supporting routing to services on shared clusters with dynamic port assignment (like ECS or Mesos). NLBs support multiple ports on same IP; registering targets by IP address, including targets outside the VPC for the load balancer; ECS can select unused port for scheduling a task then register a target group using this port. - CLBs are supported in EC2 Classic as well as in VPCs while ALBs are supported in VPCs only. - ALBs can target groups of instances and IP based targets in the RFC1918 ranges allowing you to use on premise destinations via VPN or Direct Connect.