I've been using an elastic IP that connects to my public IP, but I've hit the limit on elastic IPs. I learned that transitioning to a Load Balancer might be the way to go. Can anyone share tips or guidance on how to set this up correctly? I've tried implementing it, but my application is completely offline right now. I'm not sure what's wrong with my load balancer setup.
3 Answers
Typically, application load balancers are designed to be internet-facing. Even though they provide an endpoint URL, they operate with one or more public IPs that don't impact your Elastic IP limit. If you're handling HTTPS traffic, set up a security group to only allow inbound traffic on port 443. If you're using TLS, don't forget to get a certificate from AWS Certificate Manager (ACM) too. The load balancer directs traffic to your back-end servers (usually located in private subnets) through Target Groups. You can set it to route requests to port 80 on the back-end servers.
I would need to check out your configurations to help you better. It's often a simple oversight that can cause issues.
Make sure to double-check your Health Check configuration in the target group. It has to point to a URL or page on your backend that returns a 200 response. That might be where the error is!
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