|
|
|
|
|
|
by ArchOversight
2070 days ago
|
|
|
Cause all my services bind to a private IP on the inside. I don't see the real IP that it is receiving traffic on. Also, if I have multiple IP's with EIP's attached so I can host multiple services (with unique IP's) I have to write automation to make sure I bind the service to the right internal private IP for the appropriate external IP address. It'd be much better if the IP address were routed directly to my EC2 instance. |
|
|
Isn't that done in a more straightforward fashion by AWS loadbalancers? AWS load balancer IPs and ports on one side, listeners on the other side talking to your instances - if the instances are also in auto-scaling groups, there's zero automation needed after you set this up.