Timelines for your convenience: 00:06 --- Hands-on Demo and Explanations on How to Create an AWS EC2 Load Balancer. 12:16 --- What is the AWS Load Balancer Stickiness? How to enable them? 15:08 --- Hands-on Demo and Explanation for AWS EC2 Load Balancer Stickiness. 20:10 --- SSL/TLS Certificates for Classic Load Balancers 23:38 --- What are Auto Scaling Groups? Visual Explanations on ASG. Click on the link below to subscribe : URL: tinyurl.com/qqebnwz
thank you earlier i was a bit confused because of the pace, but the recaps in the end and going back to previous videos i slowly understand it all. keep it up .
Subbed and would definitely recommend your channel - really appreciate it for giving a real world scenarios and providing a step-by-step guide of implementation
Hi Dear,Thanks for sharing Nice tutorials.My understanding is that cross AZ is not supported in Application Load Balancer. If i am wrong then we are missing that part in this hands on.Please clear
Hi Girdhar, as per what i had read and implemented, i remember having a cross az load balancer, In cross-zone load balancing, the nodes for your load balancer distribute requests from clients to the registered targets. When cross-zone load balancing is enabled, each load balancer node distributes traffic across the registered targets in all enabled availability zones. It will depend on the targets registered. For the tutorial i believe its for a single load balancer with targets registered across az. But its quite possible. I can make one video with multi az load balancing. Thanks for the input friend !!
Hi Sir, while explaining Stickiness you said we can route based on the endpoints like /Login/Users/Prod(20%) to one instance and /Home/About(20%) and remaining 60% to third instance. Can you explain how can we do it. I understand ELB Stickiness allows us to route Users to one instance for some time(Ex : 20 seconds) but how can we route/configure based on endpoints ?
Hi i have an question, so can we have more than 1 ALBs in an AZ ? and so for all AZs DNS name will remain same but IPs would change for Load balancers right ?
That also depends on the design, mostly its is about having an ALB per AZ for your application, ALB1 in AZ1 and ALB2 in AZ2, ROUTE53 can route traffic based on the health of the ALB as per your configuration, or you can change it to divert only to one out of 2.
First the instance should be running when you add it as a Target. The load balancer stops routing requests to an instance as soon as it is deregistered. If demand decreases, or you need to service your instances, you can deregister instances from the load balancer. An instance that is deregistered remains running, but no longer receives traffic from the load balancer, and you can register it with the load balancer again when you are ready.
You can have elbs spread across multiple az and az zones, the idea is to cover the ec2 instances in the target group. And there could be multiple apps hosted in the same region, so yes u can have multiple elbs
Timelines for your convenience:
00:06 --- Hands-on Demo and Explanations on How to Create an AWS EC2 Load Balancer.
12:16 --- What is the AWS Load Balancer Stickiness? How to enable them?
15:08 --- Hands-on Demo and Explanation for AWS EC2 Load Balancer Stickiness.
20:10 --- SSL/TLS Certificates for Classic Load Balancers
23:38 --- What are Auto Scaling Groups? Visual Explanations on ASG.
Click on the link below to subscribe :
URL: tinyurl.com/qqebnwz
When i try to connect the load balancer over the internet, respond as "503 Service Temporarily Unavailable" please advice. Thanks
thank you earlier i was a bit confused because of the pace, but the recaps in the end and going back to previous videos i slowly understand it all. keep it up .
Subbed and would definitely recommend your channel - really appreciate it for giving a real world scenarios and providing a step-by-step guide of implementation
Thanks much !!
Super nerdy jokes about auto scaling, but I liked them :). Good job.
WOW so many things learned regarding load balancing. I think each and everything is covered in this tutorial
Thanks sir
Fantastic.
Auto play is working in sequentially.
Thanks a lot.
Enjoy ✅
Amazing & in-depth discussion
That's some good content. Thanks!
Awesome information ❤️
Hi Dear,Thanks for sharing Nice tutorials.My understanding is that cross AZ is not supported in Application Load Balancer. If i am wrong then we are missing that part in this hands on.Please clear
Hi Girdhar, as per what i had read and implemented, i remember having a cross az load balancer,
In cross-zone load balancing, the nodes for your load balancer distribute requests from clients to the registered targets. When cross-zone load balancing is enabled, each load balancer node distributes traffic across the registered targets in all enabled availability zones.
It will depend on the targets registered. For the tutorial i believe its for a single load balancer with targets registered across az. But its quite possible. I can make one video with multi az load balancing.
Thanks for the input friend !!
12:00 we are the magicians!!!! xd xd
😄😄😄
Hey I have a question about the certificatons @@Pythoholic
Super awesome
Hi Sir, while explaining Stickiness you said we can route based on the endpoints like /Login/Users/Prod(20%) to one instance and /Home/About(20%) and remaining 60% to third instance. Can you explain how can we do it. I understand ELB Stickiness allows us to route Users to one instance for some time(Ex : 20 seconds) but how can we route/configure based on endpoints ?
I wanted to refer it as a provision that could be used along with the route 53 to have this level.of control keeping her DNS behind the load balancer.
hi sir. Thanks for the course and all the info for free. can you upload update videos on SAA-CO3 i want to appear the exam next month.
Yes, i will update the videos on that. thanks
Hi i have an question, so can we have more than 1 ALBs in an AZ ? and so for all AZs DNS name will remain same but IPs would change for Load balancers right ?
That also depends on the design, mostly its is about having an ALB per AZ for your application, ALB1 in AZ1 and ALB2 in AZ2, ROUTE53 can route traffic based on the health of the ALB as per your configuration, or you can change it to divert only to one out of 2.
@@Pythoholic Okay Got it. thanks
Hi i have one more Query. suppose i wanted to test resiliency of Load balancers. how can we test ? can we disable an load balancer on an AZ say A
what happens if you specify load balancer with 3 AZ but the target instance is not created in one of those AZ.
First the instance should be running when you add it as a Target. The load balancer stops routing requests to an instance as soon as it is deregistered. If demand decreases, or you need to service your instances, you can deregister instances from the load balancer. An instance that is deregistered remains running, but no longer receives traffic from the load balancer, and you can register it with the load balancer again when you are ready.
Can we have multiple ELBs for single AZ or multi-AZ?
You can have elbs spread across multiple az and az zones, the idea is to cover the ec2 instances in the target group.
And there could be multiple apps hosted in the same region, so yes u can have multiple elbs
While replacing instance security group rule with load balancer security group rule , not able to get the page on internet.. please help to resolve
Check each connection point carefully. Would advice redoing it on paper and then on the console.
It was great
@pytholoic Videos on this playlist is shuffled and not in sequence as it was earlier. Which is also not good if someone is starting new.
Thanks neetu let me fix it
please check it again and let me know
@@Pythoholic Its working now
I didn't get a cookie for the session 😅
Can u give me the script of nginix?
Please search for pythoholic github. It's on github itself
@@Pythoholic can u share the link please?
github.com/Pythoholic/pythoholic_demo_aws/blob/master/demo_ec2_user_data_scripts/install_nginx_server.sh