I have been trying to set up a network ELB on AWS so that traffic arriving on the configured elastic I.P gets forwarded to a healthy instance on the TCP port it is directed at. So incoming traffic for port 80 gets forwarded to a healthy instance on port 80, and incoming traffic for port 443 gets forwarded to a health instance on port 443.
From trying to configure this it seems to want an elastic I.P address per port. This makes no sense, I am able to do this on internal infrastructure with Pacemaker and on Google Cloud, I could do this 4 years ago. Am I missing something?
What I ultimately want is handle HTTP and HTTPS traffic and to terminate SSL with my services to an application level ELB will not do. I then want DNS traffic arriving at a configured elastic I.P to get to a healthy node. A super common use case, but can't manage to see how it will work with AWS network load balancers.