Mastering AWS Network Load Balancer | ALB vs NLB | Step by Step Tutorial - Part 18

preview_player
Показать описание
▬▬▬▬▬▬ 🗓️ Book Me for Consultation ▬▬▬▬▬▬

▬▬▬▬▬▬ 🙍🏻‍♂️Join Membership ▬▬▬▬▬▬
Join this channel to get access to perks:

▬▬▬▬▬▬ 🚀 Top resource to learn Cloud Computing ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Courses ▬▬▬▬▬▬

▬▬▬▬▬▬ 📖 Video Description: ▬▬▬▬▬▬
🚀 Dive into the world of AWS Elastic Load Balancers (ELB) with our latest tutorial! In this comprehensive guide, we'll walk you through the process of creating a Network Load Balancer (NLB) on AWS and explore the nuances of Application Load Balancer (ALB) with path-based routing rules.

Also Network Load Balancer offers - TCP and UDP Load Balancing, Target Groups and Health Checks, Cross-Zone Load Balancing, Source IP Affinity, High Performance and Scalability

🔧 Timestamps:

0:00 - Introduction : Understand the importance of Load Balancers in a scalable and reliable AWS infrastructure.
2:03 - Setting up Networking : VPC, Subnet, Intergnet gateway, Route Table, EC2
25:30 - Setup Targetgroup for Network Load Balancer
27:55 - Setup Network Load Balancer (NLB)
33:16 - Key Differences: NLB vs. ALB | Path-Based Routing with ALB

👍 Don't forget to like, share, and subscribe for more AWS tutorials and hands-on guides! Master the art of load balancing with AWS ELBs and elevate your cloud infrastructure to the next level. #AWS #LoadBalancing #NLBvsALB #CloudComputing
Рекомендации по теме
Комментарии
Автор

Hello Rahul, I don't know how you have this much patience to explain everything in every video. This is the best channel I have seen in YouTube till date for AWS. Thank you for your efforts...!!!

SrinivasD-treh
Автор

You are the man! Thank you so much for all of these videos!

efuchsman
Автор

I appreciate the video, it helps with the overall understanding of the LBs in general. Couple of feedback that I would like to share: 1) Internet Gateways are VPC specific and not subnet specific so, possibly it will make more sense to attach it to the VPC rather then the Subnet. 2 ) Why not use Auto scaling group as it will help in a complete architecure set up and a good point of using LBs as well. Other than that, I really enjoy the video! Keep up the good work! Thanks

fintech
Автор

Thanks Rahul bro.... put AWS complete video with hands on bro.... i saw your aws course keep posting

surenkumars
Автор

ALB VS NLB contents are very rare… thank you very much!

Also, have a request to have another content on OpenShift in-depth hands on using AWS cloud. 🙏

Learn_IT_with_Azizul
Автор

Hi Rahul,

Your teaching skills is excellent. We need more skilled teacher like you.❤️

I'm requesting you to please create detailed Kubernates video like this for CKA.


Thanks
Shubham Tiwari

shubhamtiwari
Автор

same thing here @rahul Can you ensure route table mentioned on the left hand side in the diagram are they correct, you mentioned /1 and /2 both side.

trendlines
Автор

27:14 - I was expecting after you chose TCP instead of HTTPS that the port to the right of the dropdown change:

- from value: 80
(which is standard for HTTPS which was initially shown as pre-selected option in the dropdown)

- to value: 443
(which is standard for TCP)

Isn't that what should have happend? Also, you mentioned "" . So why is it that at 27:23 health check remains on HTTPS... and how come this didn't give any errors subsequently?

I tried answering these questions on my own and I came up with: TCP & HTTPS are actually not "antonyms" let s call them. Actually TCP operates at layer 4 in the OSI ISO model and HTTPS operates at layer 7. Also HTTPS operates on top of TCP. Basically: when you access a website, your browser uses HTTP (Layer 7) to request web pages. HTTP uses TCP (Layer 4) to ensure the data is transmitted reliably.

Also at 34:31 port 80 actually now shows up as port 81... was that something automatically done by AWS?

other observations / questions:
- 35:15 Application* Load Balancer just to make it crystal clear
- 37:11 in other words: we are simulating our application has multiple responsibilities; and you are showing us how we can leverage ALB to basically separate these different responsibilities (2 responsibilities in our case) of our application across different endpoints (in our case they are actually different machines!!) of ours. Nice!
- 45:55 why is weight 1 okay? Shouldn't we route 100% of requests whose ending path end in "foo" to that "foo-tg-alb" target group?

munteanionut
Автор

Thanks Rahul.
This video is more informative.
Really, This helps me a lot to clear some small doubts 😊

ShashiKumar-jcgy
Автор

Thanks for the videos Rahul, very informative.

kammellapradeep
Автор

Thank you soo much for your valuable knowledge sharing ☺

RVI-wp
Автор

Amazing work and detailed one. Thanks for that. Just wondering what tool do you use to make diagram and associated animations?

muralitharanvasudevan
Автор

Great Explanation😍, Thanks.
Please do more such videos with graphical view.

NANINANI-ixuf
Автор

Thanks for the informative tutorial. Great ❤

supun_sandaruwan
Автор

Thanks @Rahul, Great content and neat explanation 👌 👏 👍

bhargava
Автор

thank you, sir, for this project I mentioned this on my LinkedIn profile🤩🤩🤩🤩

secretofallthings
Автор

such wonderful videos. thanks for the videos .i understand better with demo

karthik.karunanithi
Автор

hi rahul bro. If we use s3 for remote statefile, can we delete state file through same terraform code as well as s3 bucket. Not manually

venkat
Автор

Excellent content, really appreciate this

rodneydias
Автор

Hi Rahul,

I have a query regarding our NLB setup. When we launch the NLB and try to access the Foo and Bar web pages, the responses are consistently coming from EC2 instance 1, rather than EC2 instance 2. I’m wondering when we can expect EC2 instance 2 to start handling requests through the NLB?

Thanks,

Sudharsan-ir