Currently, in Create Listener:
.... Next you will need to click on Add Listener to create a second Listener. This listener will use port 8443
I'm not sure the purpose of this. But, if this is supposed to handle an API request (Kill Bill backend) from internet, like various Kill Bill clients, etc. I think this is won't work.
Since Kill Bill and KAUI use the same Load Balancer (and thus sharing the same Load Balancer's DNS name, like kbhp-loadbalancer-XXX.us-east-1.elb.amazonaws.com), we can't register killbill backend to domain registrar CNAME because CNAME only support <host>. We can't set <host:port>.
Furthermore, If we remove port 8443 listener above, this section in Create Target Group should be updated as well:
Next, you need to perform the same steps for the second listener. This listener will handle messages directed to the Kill Bill server ....
Solution: If the purpose of creating listener in port 8443 is to make killbill API available to internet, I think the correct action would be Creating 2nd Load Balancer, just for Kill Bill API.
Currently, in Create Listener:
I'm not sure the purpose of this. But, if this is supposed to handle an API request (Kill Bill backend) from internet, like various Kill Bill clients, etc. I think this is won't work.
Since Kill Bill and KAUI use the same Load Balancer (and thus sharing the same Load Balancer's DNS name, like
kbhp-loadbalancer-XXX.us-east-1.elb.amazonaws.com), we can't register killbill backend to domain registrar CNAME because CNAME only support<host>. We can't set<host:port>.Furthermore, If we remove port 8443 listener above, this section in Create Target Group should be updated as well:
Solution: If the purpose of creating listener in port 8443 is to make killbill API available to internet, I think the correct action would be Creating 2nd Load Balancer, just for Kill Bill API.