2 ms·
Ok, ip mode seems usable if you don't have a lot of connections per NLB/instance pair, but kind of meh. Does the instance port have to match the service port?
by toast0 6y ago
Ok, ip mode seems usable if you don't have a lot of connections per NLB/instance pair, but kind of meh.
Does the instance port have to match the service port? In instance mode, you could setup so us-east1 is like 441, us-east2 is 442, us-west1 is 451 etc. And then you wouldn't have tcp 4-tuple collisions on the instance.
Similarly for ip mode, you could put the same host in for ports 440-449 and get 10x 55,000 connections, or however many ports you need to hit your numbers.
(Port numbers chosen for example only, check /etc/services if you don't want to stomp on allocations for services you're probably not using)
Thanks!
- benmmurphy 6y agoThat AZ-port solution would work as well and would be easier to configure than different IPs. But they don't let you map port or IP based on AZ for a single NLB. You could setup different independent NLBs in each zone and then setup target groups for each NLB AZ and I think this might have been what you were proposing. I'm pretty sure you can setup a different port for each target group and it doesn't have to match the traffic port on the NLB. For IP mode you are correct that you can run on multiple ports to get around the connection limit. The documentation even says it is based on IP address and port. > When the target type is ip, the load balancer can support 55,000 simultaneous connections or about 55,000 connections per minute to each unique target (IP address and port). If you exceed these connections, there is an increased chance of port allocation errors. If you get port allocation errors, add more targets to the target group. https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html https://docs.aws.amazon.com/elasticloadbalancing/latest/netw...