News for hackers. Stuff that matters.

A comment on AWS and their billions in IPv4 addresses. Parent comment

Re:AWS and their billions in IPv4 addresses by ArchOversight on Tuesday October 20, 2020 @11:03PM (#24844387)
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.

[ Parent | on HN ]
Re:AWS and their billions in IPv4 addresses by outworlder on Wednesday October 21, 2020 @08:30PM (#24853797)
> I have to write automation to make sure I bind the service to the right internal private IP for the appropriate external IP address.

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.

[ Parent | on HN ]