Great video, thank you! And the best part was that you took the time to show exactly how to get rid of the resources, in order, so that you don't end up owing money to AWS.
I love videos like these where the creator really cares about the audience enough to go the extra miles and create content which is intuitive and easy-to-understand. Thanks to that Spirit of care. God bless.
i need to say, this was the most incredible way to explain how this works, even after working several time with aws i never got to understand alb like now. tks!
Thanks for the clear explanation. I really love the way how you enjoy teaching things with a bright smile on your face. Makes the learning process more fun and easy.
Teaching made simple ,As a beginners, I struggle to understand some hand on but with Tiny understanding is made simple, Thanks for taking time to make videos.
You are the one of the best teacher i have ever met on youtube.. your lessons are very clear and you have attractive voice also.. if you can please make more lessons like this about AWS..
Awesome Awesome Awesome!!! You have a definite gift for explaining and teaching technical subjects! This tutorial is the best I've run across yet in my cloud practitioner studies. This subject could not have been explained and demoed better! Thank you so much once again and I'll see u in the next one!!! Cheers!
Sam - You are awesome, awesome, awesome for leaving such a nice comment!! Thanks so much...this made my day! Really glad you're enjoying the videos! :)
Hi Amber. Awesome tutorial. I cannot thank you enough for the work you do. I just love the way you explain in simple manner. Currently, I'm taking your AWS CCP course on ZMT and able to understand all the concepts. Thank you so much!! Keep up the good work!
Thanks so much, Antony! 😊 There's definitely some good coverage of topics here on the channel. For full SAA prep, though, you can check out my course on Zero to Mastery: academy.zerotomastery.io/a/aff_464yrtnn/external?affcode=441520_lm7gzk-d. It goes into more depth, and also has lots of practice questions to help you prepare for the exam. Hope that helps! Let me know how the test goes. 😊
This is by far the best video I have come across on this topic! Well done, Amber! Thank you for lucidly explaining along. two questions: 1. At 13:00, if you kept hitting refresh, would it toggle the network traffic across the 2 instances in TG-2, or go to just that 1 instance? 2. How would you set this up so the network will randomly go to any of the instances across both the Target Groups? Thanks so much, Happy Holidays! 🙂
Thanks for the nice comment, @sraj7284, and Happy Holidays to you too! 🎅🎄😊 1. It would toggle the traffic across the 2 instances in TG-2. 2. I'm not aware of a way to set it up to randomly distribute traffic across Target Groups. In the rules, you have to specify the % distribution for traffic, so it would adhere to those numbers. Hope that helps! 🤓
@@TinyTechnicalTutorials Looks like I did not ask the right question. What I really wanted to ask was, how to distribute load across different AZs, because it appears that the nodes in each AZ will send traffic to just its own target groups. Looks like there is a setting called "Cross Zone Load Balancing" that sends traffic to all AZs. Its enabled by default. You would have to go to each target group to take it out of the Cross Zone load balancing, if you didn't desire this setting. Wish you a very happy, healthy, prosperous and fulfuling 2024 ahead! 🙂
Hi Harshal! Yes, you can route traffic to different ports/different target groups. Here are a couple links that might help? stackoverflow.com/questions/56877149/aws-load-balancer-to-route-traffic-to-one-target-group-with-multiple-microservic stackoverflow.com/questions/61999337/aws-elb-routing-http-https-traffic-to-a-custom-port-of-ec2-instance bharathi-batthula6.medium.com/aws-applicationload-balancer-e03f4f386a9d
Hi, smooth as always, thank you! My questions for you: 1) If we add route 53 to the mix (referring to your video), will the DNS get resolved to the ip address of the load balancer or the actual instance that processed the incoming request? 2) My understanding is that we created the ALB nodes in multiple AZs - is this optional and for HA and fault-tolerance reasons. Or we could also choose to create a singular ALB node instance (in one of the AZs where our TGs/instances are running)? 3) If we chose to create ALBs (node) in multiple AZs, will the incoming traffic gets distributed to ALL of nodes (based on some algorithm) or is it only ONE node that still receives all the traffic and does the distribution to the TGs?
Hi Praveen! I haven't forgotten about this one! 😊 1) If you add Route 53, you'll want to create an "A" record/alias that points to the load balancer. While in theory you could point it to a specific instance if you knew the IP, the point of having a load balancer is so that IT can route traffic to the instances, it can do health checks, etc. (you can also set up an SSL certificate, use WAF on it, etc.). So pointing to the load balancer is the way to go. 2 & 3) For the application load balancer specifically (vs. network load balancer or classic load balancer), you're required to choose at least 2 AZs. There's a pretty good description/diagram here about how routing works across AZs: docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html Hope that helps!
Hi DM! 😊 Load balancers are region-specific, so it's not possible to route to a second region with *just* a load balancer. To go cross-region, you'll need to use Route 53 (which is a global service, and can therefore route across different regions). Here's some more information: docs.aws.amazon.com/whitepapers/latest/real-time-communication-on-aws/cross-region-dns-based-load-balancing-and-failover.html
i have one doubt can i add more listeners in a load balancer and connect it with different domains under one load balancer because when i try to do that i am getting another error when trying to access the response that the ssl remains to another domain that i have hosted first could you help me!.
Hi Aayush! Yes, you can use a personal AWS account. If it's a relatively new account, you should still be on the Free Tier for most things, and then some things are always free. Here's more detail if you want to check anything specific: aws.amazon.com/free Hope that helps! :)
Thanks for the kind words, Luca! 😊🙏🌟 Glad you liked it! Yes, you can do a similar setup with a network load balancer, though the configuration is a bit more involved (protocols, ports, IPs, etc.). But maybe this will get you started? docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html
Ooh, good question! 🤓 Yes, they'll persist even after deleting the instance. You can have multiple instances using the same security group. So if Instance A and B were both using the same security group, you wouldn't it to be deleted if one of the instances was deleted.
Hi Raju! You're right...this video doesn't go into the rules for host- and path-based routing. Here are some links that might help instead: -Host-based: aws.amazon.com/premiumsupport/knowledge-center/elb-configure-host-based-routing-alb/ -Path-based: aws.amazon.com/premiumsupport/knowledge-center/elb-achieve-path-based-routing-alb/
Hi Ali! 👋 It's technically possible to do this, but could make it more difficult to identify and troubleshoot if there are issues. And obviously there would be a single point of failure. There are some good points here in this thread to consider as well: stackoverflow.com/questions/65447698/aws-alb-single-for-all-services. Hope that helps! 😊
@@TinyTechnicalTutorials Thank you very much for taking my question into consideration! I've checked the link you provided and I also want to extend my gratitude to them for sharing their ideas. I agree with you regarding the concern about a single point of failure. However, I also need to consider the trade-off between costs and complexity, as is often the case. Regardless, I greatly appreciate your videos and have learned a lot from them!
@@TinyTechnicalTutorials Hello Amber, another question comes up: Consider this: I would like to use a single set of EC2 instances and assign them to two or more target groups for utilization across two or three ALBs. Each ALB would have its corresponding target group, as these instances are meant to be allocated to two or three different target groups. This setup ensures redundancy: if one of the ALBs becomes unavailable, the others can continue functioning. Furthermore, all EC2 instances should remain reachable. Is this scenario reasonable, or are there drawbacks to consider? Given that DNS (Route 53) is internet-facing and the ALBs must be positioned behind other ALBs, the question arises of which services or load balancers should be interposed between the ALBs and DNS. Is it advisable to use wildcard DNS? In this context, the query remains: How can incoming traffic from external sources navigate through DNS and then be accurately directed to the correct ALB with its associated target groups?
Every AWS tutorials seems to focus on the most basic example like HTTP target group on port 80.. Unfortunately not very helpful to the complexity of what needs to be done in real world production apps..
Your meaning of host header is wrong , if the traffic for accessing a website then route to this target group not if the website source is this then route the traffic
