Application Load Balancer Setup to Point to Your AWS EC2 Instance
HTML-код
- Опубликовано: 15 фев 2023
- Now that you have a website up and running on your AWS EC2 instance, it is time to setup a load balance which will take care of managing traffic, allowing our domain to function properly and to automate SSL without breaking a sweat. AWS Application Load Balancers are very powerful and have made a big difference to my hosting workflow. They are one of the reasons I like to host my site on AWS.
This tutorial helped me a lot to setup the load balancer quickly for my app. Real life saver. Thank you so much❤
I've been trying to set up unsuccessfully my website with a load balancer to serve HTTPS and you saved me! Thank you a lot!
Thanks for this video,
this is exactly what I needed, I've been on this for over 4 days now
Amazing! Really glad it helped you and believe me when I say...I know the feeling!
Solid tutorial here... Followed along till the end from the previous video..
Would love for a tutorial hosting on ecs, thanks
Excellent tutorial, it helped me a lot... thanks buddy!
This tutorial was great! Thank you!!!!
Thanks for the positive feedback!
Excellent content
Thanks mahn, this video really helped me.
Great to hear!
thank you very much for your video
Glad it was helpful!
I have struggled in this video , i got solution, thanks you very much
Glad to hear that you figured it out!
@@coderaiders-yt I will try this solution
Would love to see VPC version of this :D
This video is very informative, thank you!!
Great tutorial! My question is what did you do with the 'u' in 'McDonough'?🤪
Perfecto
Thanks a lot. Now, considering that public IPs are chargeable, would be interesting to see an update of this running with EC2s without public IPs, behind ALB.
use elastic IP on your EC2 instance
@@stefanbe5138 those are chargeable
Another great video. Thabk you for your time
Do you have a link to the information you mentioned for hosting on a private subnet?
Also, a video showing stripe/paypal integration would be very interesting.
You might find this useful: ruclips.net/video/hO036v4NvQI/видео.html
once you create that hosted zone you need to by that domanin from registered domains or this method is completly free ?
Which rules does the "allow-public-internet-access" security group contain?
This was helpful. If my EC2 app is already using Gunicorn and Nginx as a reverse proxy can I still use your method of wrapping with ELB? My understanding of how those port configurations might conflict is thin so I’d appreciate any context.
If you are doing it solely on your one instance and using a load balancer within NGINX, you would need your applications to run on something like docker. If you are using NGINX as a reverse proxy and then using the AWS ELB to point to your machine, I see know reason why this would not work. But you can test it. If you see the website showing when putting in the public domain with http (notice I did not say https, so my.ip.address), then it is working and the ELB should point to it.
thank you for your video. I have just one question. When creating A record (09:32), I already have one A record for redirecting traffic to IP (Public address of EC2). I cannot create another A record.
If I understand correctly, it is best to have one A record pointing to the load balancer, then have the load balance perform the redirect to whichever target groups you set up.
Great
💪
at 2:20, why not use HTTP/2 instead of HTTP/1.1?
I have an EC2 instance with two docker containers - frontend nextjs and backend nodejs.
I have given frontend code our backend IP address with port. Now, that IP shows up in network in devtools.
How would you suggest I tackle this? What are the best practices.
I have similar problem where i have 2 container of multistage docker React with Nginx and nodejs. They both are connected in http but when i try to apply letsencrypt using an external default,conf file to run as docker compose file along with the SSL certificate to be coppied into the container wile running, is such a mess. thats why this video is helpfull ofr me where you can buy SSL certificate using ACM and route 53 where the SSL is applied to the ALB and then SSL terminatino can happen without us needing to touch the instance or the running container.
What is source ip to communicate target instances??
I just cannot get the load balancer to work.
I progressed well to the end, but couldn't create an a record for the alias settings because there's an existing A record connected to the IP address from ec2. any kind of assistance is appreciated.
You can try having just one A record pointing to the load balancer. If using NGINX, make sure it is pointing to localhost, or the private IP address (not the public one). Not sure if this helps.
can you reveal the Security group you used in this video please
Love your videos,
i'm getting a 502 error after following this steps, is there a solution for this?
502 will mean that probably when NGINX is trying to point to, is not running. Test the application is running first.
Does your backend server for your website also exist on ec2 instances?
Yes. I find EC2 the best value for money.
I followed your way, but still not redirecting to https
Hello thanks for your tutorial, Ihave a trouble with this error : ERR_SSL_PROTOCOL_ERROR,
Please i need help if you can, thanks in advance.
Hi there did you get this resolved?
my requested certificate is not coming in the dropdown
Hmm... a lot of thing doesn't make sense. The ELB is pointing to EC2 which contain self copy of rproxy, frontend and even backend. If there are 3x EC2, there are 3x self copy of rproxy, frontend and even backend...
There are not x3 EC2. Just one. But if you run 3 EC2, you can have load balancer rotate in pointing to them.
You configured 80 to 443 redirection, but you haven't demonstrated that.
Also on 8.13 you say that http will forward to https which is not true. It seems that you do not understand the difference between forwarding which means mapping or converting from one port to another thus disabling the forwarded port whereas redirect does not.
The load balancer is set up to receive requests in at port 80 and there is a redirect set up to go to port 443 on the port 80 configuration of the load balancer.