I'm surprised that you don't have more likes. You are very organized, very clear and concise, and have a great vocal tone in your delivery. That's an 'A' in my book. Keep up the great work.👍
Awesome Awesome Once again!!! And wanted to let you know I passed My Cloud Practitioner exam yesterday!!! Thank you for all of your help and I look forward to you Solutions Architect material coming soon! Cheers!
SAM!! That's AMAZING!!! Congratulations!! Thanks for letting me know! I'm putting the final touches on the Architect course...and still have a reminder to let you know when it goes live. For now, go celebrate! :)
I just love the how you make everything so simple, as a Cloud Devops engineer managing other clients' aws infrastructure, I come to you to unclutter my brain with these services. Keep up the good work. Can you point me to a good aws route 53 and eks video? Thanks again
Oh, you're too kind! 🥰 Thanks for such a nice comment. I'm glad the videos help! I have a Route 53 video here that you might like: ruclips.net/video/JRZiQFVWpi8/видео.html. I don't have any on EKS yet, but skimmed through a few videos on RUclips. This one seems pretty easy to follow if you're just getting started: ruclips.net/video/CukYk43agA4/видео.html Hope it helps! Thanks again for supporting the channel! 🤓🌟🙏
Hi Tyler! 👋 Sorry for the slow response! Here are steps to do a blue/green deployment (with a little help from ChatGPT 😊): 1. Create Two Auto Scaling Groups Blue ASG: This is your currently running production environment Green ASG: This will be the new version of your application you want to deploy 2. Set Up Elastic Load Balancer (ELB) Create an ELB that will route traffic to the ASGs Register the instances of the Blue ASG with the ELB 3. Deploy the New Version Create the Green ASG with the new version of your application Ensure that the Green ASG's instances are healthy and fully initialized before proceeding. 4. Switch Traffic to the Green ASG Update the ELB to register instances from the Green ASG Deregister the instances of the Blue ASG from the ELB This step should be done gradually if you want to perform a phased switch, using health checks and monitoring to ensure the new instances are handling traffic correctly 5. Monitor the Deployment Monitor the performance and health of the Green ASG instances using CloudWatch, ELB metrics, and any application-specific logging Ensure there are no errors and that the application is performing as expected 6. Clean Up (if successful): If the Green ASG deployment is successful and stable, you can terminate the Blue ASG Optionally, keep the Blue ASG for a period of time as a fallback in case issues arise 7. Rollback (if necessary): If issues are detected with the Green ASG deployment, roll back by updating the ELB to re-register instances from the Blue ASG and deregister the instances from the Green ASG
Hi @rrp2600! 👋 AWS does its best to distribute your instances in a way that they're spread across the underlying hardware, but you don't have a way to know the details for sure. However, you CAN influence placement by specifying a Placement Group. Here are more details for those: docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html. Hope that helps! 😊
Hello, I like your session on Load Balancer. I have a question - Did you create Private instance or Public facing instance? I have not seen you enabled a Public IP for the instance during Launch Configuration Template. Also you have not selected key pair for instance, so without key how an Instance gets connected?
Hi Vijji! 👋 I've got "Auto-assign public IP" enabled for all my EC2 instances (under "Network Settings" when I go to create a new instance), so I didn't have to manually do that. I believe this is the default setting when creating things in the default VPC, though you can override it. And you're right about the key. You'll need that to log into the machine, but I didn't need to log in for that video so I skipped it. But it IS recommended that you have a key. Hope that helps! 😊
Hi TTT, your videos have helped me tremendously for school. In comparison to your previous Load Balancing video, where you created two original EC2 instances, is that step no longer necessary for Auto Scaling? It seems that with Auto Scaling, I no longer require the "original two EC2 instances" and just let Auto Scaling generate or destroy instances as long it meets the minimum number of instances I set. Thank you!
Hi Yoram! Thanks for the nice comment! I'm so glad the videos are helpful. :) You are correct...with Auto Scaling, the Auto Scaling Group handles creating/destroying the instances. That's one of the big benefits: you don't have to manually provision, configure, terminate, etc. It just magically happens based on the number of instances you set (or based on some metric like CPU usage, etc.). You got it!
Hi Javier! 👋 There are actually several different ways you can scale (regardless of whether you're also running an ELB). It's possible to scale based on demand, like the capacity percentage you mention. That would be "Scale based on demand" mentioned here: docs.aws.amazon.com/autoscaling/ec2/userguide/scale-your-group.html#scaling-options. But there are other options as well. Really depends on the workload as to what makes most sense. Hope that helps. Thanks for watching! 🤓🙏
Question, the security group you created for the launch template, you allow traffic from the world, which is not a best practice for using a load balancer, because clients can still directly access all EC2 instances. I was wondering what would be the architecture that the SG for backend EC2 only receive internet traffic from ALB
Hi @asd855280! 😊 It's a great question. You're 100% correct...in the real world, you wouldn't want to open up the security group to the world. You'd have "the world" hit a load balancer. Then for backend EC2 instances, yes, you can set up the security group to only allow traffic from the load balancer (when you set up the security group, there's an option to select "load balancer" rather than specifying a port range). Hope that helps. Thanks for watching!
Hi, in the step of attaching the auto scaling to an existing load balancer. If you put two existing load balancer target groups there. What will happen? Will the instances created by the auto scaling going only into one of the group or both?
Hi Yi! Thanks for watching! 😊 If you associate two target groups with the Auto Scaling Group, when a new instance is created (by the ASG), it will be registered with both target groups. And when the instance is terminated, it will be de-registered from both target groups. Here are a couple links that might help: stackoverflow.com/questions/59916924/attaching-a-target-group-of-alb-to-an-auto-scaling-group stackoverflow.com/questions/48529074/how-is-target-groups-different-from-auto-scaling-groups-in-aws
Hi Brad! 👋 Here you go! #!/bin/bash # User data for new EC2 instances # install httpd (Linux 2 version) yum update -y yum install -y httpd systemctl start httpd systemctl enable httpd echo "Hello World! This is $(hostname -f)" > /var/www/html/index.html
Hi, thanks for the tutorial. I tried setting up ASG but failed every time. The issues I am facing are: 1. The instances getting created after creating the template are not getting auto registered in target group. 2. If I try to open the URL for load balancer, I get the error: Bad Gateway. 3. The "autocreated" instances are getting terminated of their on and new instances keep getting launched. This cycle of launch and termination keeps happening. Could you help in letting me know where I am missing anything ?
Hi Rajesh! 👋 Hmmm...I haven't run across these issues before, but maybe some of these links will help? 1. Check your instances and load balancer are in the same availability zone: stackoverflow.com/questions/59398798/automatically-registering-targets-with-a-target-group-in-aws 2. Some common troubleshooting for "bad gateway" errors: repost.aws/knowledge-center/elb-alb-troubleshoot-502-errors 3. I think this might be (??) related to the issues above? Hope this helps! Feel free to report back here with any solutions...I'm curious! 😊
@@TinyTechnicalTutorials Hi TTT, thanks for your response. The good news is that the major issue has been resolved. I feel that it was a mistake at my end while the template was prepared. Since the template creation process does not give any option to enable/disable the public IP of newly created EC2 instance, so whatever instances were getting created, none had the public IP allocated to them. I created a template from an existing EC2 and used in proceeding further. It worked perfectly - I tested by increasing the CPU utilization to more than the threshold defined in configuration and the new instances got created promptly i.e. scale out is happening as expected. However one last issue is still not resolved - when I reduced the CPU consumption to less than the threshold, none of the EC2 got terminated.That means the scale-in is still not happening. Would appreciate any help in getting scale-in configured properly.
Hey great work thank you. What is the magic involved with VPC's and Ip Addresses / CIDR blocks? Although some Dev Ops tasks seem straightforward from exposure to CICD and Cloud Formation that VPC SubNet math is weird coming from a developer or App Arch point of view. I mean you didn't mention anything in this about Route 53 or NACLs or all that routing jazz that troubles me soo much specifically ---> OK Never Mind you did it already thank you ruclips.net/video/7_NNlnH7sAg/видео.html How does one GROK that number after the slash / in a CIDR block ? So I make my VPC and I define some IP "RANGE" I pick a series of octets and want lets say 100 Ip Addresses TOTAL in the VPC and 50 of those I want to segment into a private subnet and 50 to my public subnet .. Blah blah some used internally for blah blah OK yeah whatever --- How to 101 basics please ? I know how to...... massage route tables and define appropriate routes POINT for various resources ALBs etc etc but that initial set of and division of IP Addresses. THE SET UP Where/what is the simple formula to figure out 000.000.0.0/ ?? Its not straight forward like octets 1-50 and 51-100 ... -- and then there is that damn slash mark. I'd basically be Dev Ops confident a-top Solutions Arch confident (AWS Certs) if I can master this concept please. -- Goes off to google "CIDR blocks and Ip address ranges for DevOps engineers , for Dummies, 101 Basics" AGAIN ! lol
Hey again, SeaC Programmer! 😊 Yeah, IP addresses/CIDR blocks can be hard to wrap your head around. In addition to that VPC video you found, I have another "basics" video about that very topic (little bit of overlap with the VPC video): ruclips.net/video/kRDtwr1dPpw/видео.html. Might help a little bit??
@@TinyTechnicalTutorials thanks for the swift reply... Already outdated MCSD, current AWS CDA reviewing for the AWS SA Pro. thanks I stumbled upon this [ AWS VPC Basics ] and it was excellent thank you . ruclips.net/video/O3fgul-fJCk/видео.html
What else do you want to learn about AWS? Let me know below in the comments!
VPC
Hi Naren! I've got a "basics" video for VPC here: ruclips.net/video/7_NNlnH7sAg/видео.html. Check it out! :)
You're a job-saver literally keep going.
Oh, I'm so glad it helped!! Thanks for watching! 😊
Please See below. Nice work thank you.
You are an excellent instructor. I followed you for the portion of ALB and AutoScaling, and you have made it incredibly understandable. Thank you!!!
you're awesome. I understood very strongly. I grasped not only just creating and using but also the underlying idea.
Hey TTT, I love the way you explain. It's simple and easy. using index.html is the most impressive part
TTT, this is such an awesome video. Very helpful, to the point, without unnecessary fluff. I love it, thank you!
Oh, fluff is the WORST!! 😂 Glad you enjoyed it. Thanks for supporting the channel! 🙏🌟💪
Thanks this is very helpful and easy, it is hard to find such good videos now a days
Yay! I'm so glad it helped. Thanks for watching, and for the nice comment!! 🙏🤓🌟
I'm surprised that you don't have more likes. You are very organized, very clear and concise, and have a great vocal tone in your delivery. That's an 'A' in my book. Keep up the great work.👍
Awwww...thanks so much!!! Really appreciate the support! 🙏🌟🤓
This was super helpful. Appreciate all your insight
I'm so glad! Thanks for watching! 😊
I like it....simple and to the point, that is how it should be thanks Tiny Technical Tutorials.
Wow, thanks SO much!! Really appreciate the kind words! 🥰🙏🌟
Thank you so much! This is the best tutorial about Auto Scaling.
I'm so glad it helped!! Thanks for watching, and for the nice comment! 🙏🤓🌟
You have a good teaching skill (It's a Gift).
Awwww...thank you SO much!!! Really appreciate you supporting the channel! 🥰🙏
Awesome Awesome Once again!!! And wanted to let you know I passed My Cloud Practitioner exam yesterday!!! Thank you for all of your help and I look forward to you Solutions Architect material coming soon! Cheers!
SAM!! That's AMAZING!!! Congratulations!! Thanks for letting me know! I'm putting the final touches on the Architect course...and still have a reminder to let you know when it goes live. For now, go celebrate! :)
@@TinyTechnicalTutorials Thank u so much! And I will do just that!!🎉
Thanks for this tutorial, really helpful
You bet! Thanks for watching! 🙏🤓🌟
Hi, all your tutorials are simple and excellent
Oh, thank you so much!! 🥰🙌🎉
I just love the how you make everything so simple, as a Cloud Devops engineer managing other clients' aws infrastructure, I come to you to unclutter my brain with these services. Keep up the good work. Can you point me to a good aws route 53 and eks video? Thanks again
Oh, you're too kind! 🥰 Thanks for such a nice comment. I'm glad the videos help!
I have a Route 53 video here that you might like: ruclips.net/video/JRZiQFVWpi8/видео.html.
I don't have any on EKS yet, but skimmed through a few videos on RUclips. This one seems pretty easy to follow if you're just getting started: ruclips.net/video/CukYk43agA4/видео.html
Hope it helps! Thanks again for supporting the channel! 🤓🌟🙏
Excellent simple explanation 👏
Thank you so much! Glad it helped! :)
Excellent explanation
Thanks so much, Penagonda! 😊
Hello! How do create a blue/green deployment through the use of ASGs fronted by an ELB?
Hi Tyler! 👋 Sorry for the slow response! Here are steps to do a blue/green deployment (with a little help from ChatGPT 😊):
1. Create Two Auto Scaling Groups
Blue ASG: This is your currently running production environment
Green ASG: This will be the new version of your application you want to deploy
2. Set Up Elastic Load Balancer (ELB)
Create an ELB that will route traffic to the ASGs
Register the instances of the Blue ASG with the ELB
3. Deploy the New Version
Create the Green ASG with the new version of your application
Ensure that the Green ASG's instances are healthy and fully initialized before proceeding.
4. Switch Traffic to the Green ASG
Update the ELB to register instances from the Green ASG
Deregister the instances of the Blue ASG from the ELB
This step should be done gradually if you want to perform a phased switch, using health checks and monitoring to ensure the new instances are handling traffic correctly
5. Monitor the Deployment
Monitor the performance and health of the Green ASG instances using CloudWatch, ELB metrics, and any application-specific logging
Ensure there are no errors and that the application is performing as expected
6. Clean Up (if successful):
If the Green ASG deployment is successful and stable, you can terminate the Blue ASG
Optionally, keep the Blue ASG for a period of time as a fallback in case issues arise
7. Rollback (if necessary):
If issues are detected with the Green ASG deployment, roll back by updating the ELB to re-register instances from the Blue ASG and deregister the instances from the Green ASG
Thank you.. This was helpful
You bet! Glad it helped! 😊
In simple setup like this would the 2 instances being running on different physical servers. Do you get that kind of redundancy even at the free tier.
Hi @rrp2600! 👋 AWS does its best to distribute your instances in a way that they're spread across the underlying hardware, but you don't have a way to know the details for sure. However, you CAN influence placement by specifying a Placement Group. Here are more details for those: docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html. Hope that helps! 😊
Hello, I like your session on Load Balancer. I have a question - Did you create Private instance or Public facing instance? I have not seen you enabled a Public IP for the instance during Launch Configuration Template. Also you have not selected key pair for instance, so without key how an Instance gets connected?
Hi Vijji! 👋 I've got "Auto-assign public IP" enabled for all my EC2 instances (under "Network Settings" when I go to create a new instance), so I didn't have to manually do that. I believe this is the default setting when creating things in the default VPC, though you can override it. And you're right about the key. You'll need that to log into the machine, but I didn't need to log in for that video so I skipped it. But it IS recommended that you have a key. Hope that helps! 😊
@@TinyTechnicalTutorials Thanks for your response!! I got it now. Appreciate your help!!
Hi TTT, your videos have helped me tremendously for school. In comparison to your previous Load Balancing video, where you created two original EC2 instances, is that step no longer necessary for Auto Scaling? It seems that with Auto Scaling, I no longer require the "original two EC2 instances" and just let Auto Scaling generate or destroy instances as long it meets the minimum number of instances I set. Thank you!
Hi Yoram! Thanks for the nice comment! I'm so glad the videos are helpful. :)
You are correct...with Auto Scaling, the Auto Scaling Group handles creating/destroying the instances. That's one of the big benefits: you don't have to manually provision, configure, terminate, etc. It just magically happens based on the number of instances you set (or based on some metric like CPU usage, etc.). You got it!
@@TinyTechnicalTutorials Ah ok I see. I will do more tinkering around then! Thanks again and take care!
You bet!
Demo project for Autoscaling.
Noted! :)
If ELB is not used, instances are only incremented when an instance reaches 100% capacity?
Hi Javier! 👋 There are actually several different ways you can scale (regardless of whether you're also running an ELB). It's possible to scale based on demand, like the capacity percentage you mention. That would be "Scale based on demand" mentioned here: docs.aws.amazon.com/autoscaling/ec2/userguide/scale-your-group.html#scaling-options. But there are other options as well. Really depends on the workload as to what makes most sense. Hope that helps. Thanks for watching! 🤓🙏
Question, the security group you created for the launch template, you allow traffic from the world, which is not a best practice for using a load balancer, because clients can still directly access all EC2 instances. I was wondering what would be the architecture that the SG for backend EC2 only receive internet traffic from ALB
Hi @asd855280! 😊 It's a great question. You're 100% correct...in the real world, you wouldn't want to open up the security group to the world. You'd have "the world" hit a load balancer. Then for backend EC2 instances, yes, you can set up the security group to only allow traffic from the load balancer (when you set up the security group, there's an option to select "load balancer" rather than specifying a port range). Hope that helps. Thanks for watching!
@@TinyTechnicalTutorials Thank you so much for this information.
Hi, in the step of attaching the auto scaling to an existing load balancer. If you put two existing load balancer target groups there. What will happen? Will the instances created by the auto scaling going only into one of the group or both?
Hi Yi! Thanks for watching! 😊 If you associate two target groups with the Auto Scaling Group, when a new instance is created (by the ASG), it will be registered with both target groups. And when the instance is terminated, it will be de-registered from both target groups.
Here are a couple links that might help:
stackoverflow.com/questions/59916924/attaching-a-target-group-of-alb-to-an-auto-scaling-group
stackoverflow.com/questions/48529074/how-is-target-groups-different-from-auto-scaling-groups-in-aws
thank you. Where can I get the user Data?
Hi Brad! 👋 Here you go!
#!/bin/bash
# User data for new EC2 instances
# install httpd (Linux 2 version)
yum update -y
yum install -y httpd
systemctl start httpd
systemctl enable httpd
echo "Hello World! This is $(hostname -f)" > /var/www/html/index.html
Hi, thanks for the tutorial. I tried setting up ASG but failed every time. The issues I am facing are:
1. The instances getting created after creating the template are not getting auto registered in target group.
2. If I try to open the URL for load balancer, I get the error: Bad Gateway.
3. The "autocreated" instances are getting terminated of their on and new instances keep getting launched. This cycle of launch and termination keeps happening.
Could you help in letting me know where I am missing anything ?
Hi Rajesh! 👋 Hmmm...I haven't run across these issues before, but maybe some of these links will help?
1. Check your instances and load balancer are in the same availability zone: stackoverflow.com/questions/59398798/automatically-registering-targets-with-a-target-group-in-aws
2. Some common troubleshooting for "bad gateway" errors: repost.aws/knowledge-center/elb-alb-troubleshoot-502-errors
3. I think this might be (??) related to the issues above?
Hope this helps! Feel free to report back here with any solutions...I'm curious! 😊
@@TinyTechnicalTutorials Hi TTT, thanks for your response. The good news is that the major issue has been resolved. I feel that it was a mistake at my end while the template was prepared. Since the template creation process does not give any option to enable/disable the public IP of newly created EC2 instance, so whatever instances were getting created, none had the public IP allocated to them. I created a template from an existing EC2 and used in proceeding further. It worked perfectly - I tested by increasing the CPU utilization to more than the threshold defined in configuration and the new instances got created promptly i.e. scale out is happening as expected. However one last issue is still not resolved - when I reduced the CPU consumption to less than the threshold, none of the EC2 got terminated.That means the scale-in is still not happening. Would appreciate any help in getting scale-in configured properly.
Hey great work thank you.
What is the magic involved with VPC's and Ip Addresses / CIDR blocks?
Although some Dev Ops tasks seem straightforward from exposure to CICD and Cloud Formation
that VPC SubNet math is weird coming from a developer or App Arch point of view.
I mean you didn't mention anything in this about Route 53 or NACLs or all that routing jazz that
troubles me soo much specifically --->
OK Never Mind you did it already thank you ruclips.net/video/7_NNlnH7sAg/видео.html
How does one GROK that number after the slash / in a CIDR block ?
So I make my VPC and I define some IP "RANGE" I pick a series of octets
and want lets say 100 Ip Addresses TOTAL in the VPC and
50 of those I want to segment into a private subnet and 50 to my
public subnet .. Blah blah some used internally for blah blah OK yeah whatever ---
How to 101 basics please ?
I know how to...... massage route tables and define appropriate routes POINT for various resources ALBs etc etc
but that initial set of and division of IP Addresses. THE SET UP
Where/what is the simple formula to figure out
000.000.0.0/ ?? Its not straight forward like octets 1-50 and 51-100 ... -- and then there is that damn slash mark.
I'd basically be Dev Ops confident a-top Solutions Arch confident (AWS Certs) if I can master this concept please.
-- Goes off to google "CIDR blocks and Ip address ranges for DevOps engineers , for Dummies, 101 Basics" AGAIN ! lol
Hey again, SeaC Programmer! 😊 Yeah, IP addresses/CIDR blocks can be hard to wrap your head around. In addition to that VPC video you found, I have another "basics" video about that very topic (little bit of overlap with the VPC video): ruclips.net/video/kRDtwr1dPpw/видео.html. Might help a little bit??
@@TinyTechnicalTutorials thanks for the swift reply...
Already outdated MCSD, current AWS CDA reviewing for the AWS SA Pro. thanks
I stumbled upon this [ AWS VPC Basics ] and it was excellent thank you .
ruclips.net/video/O3fgul-fJCk/видео.html
Awesome--thanks! 😊