I've been using an elastic IP linked to my public IP, but I hit the limit on elastic IPs. I learned that switching to a Load Balancer could be the solution. I've tried to set it up, but my application isn't coming back online at all. I'm really unsure what I'm doing wrong in the configuration of the load balancer. Can anyone share some tips or guidance?
3 Answers
Usually, application load balancers are designed to face the internet. They come with an endpoint URL, but underneath, there are public IPs that incur charges yet don’t count against your Elastic IP limit. If your load balancer is handling HTTPS traffic, ensure you’ve set up a security group to allow inbound port 443. Plus, if you're terminating TLS, you'll need to get a certificate from ACM (AWS Certificate Manager). The load balancer directs traffic to backend servers, so configure your target groups accordingly. Typically, you'd forward requests to port 80 on those backend servers.
I’d need to see your configurations to help you out. Sometimes it's all in the details! Let’s figure this out together.
Make sure to check the Health Check settings in your target group. It needs to hit a specific URL on your backend servers that returns a 200 status code. That’s often where things go wrong!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures