AWS Application Load Balancer with Auto Scaling group | Auto Scaling policies:Step by step tutorial
HTML-код
- Опубликовано: 23 авг 2024
- In this session you will learn how to setup aws application load balancer with auto scaling group.
You will also get knowledge on different types of autoscaling policies. I have demonstrated autoscaling policies in action.
Install stress utility using following command : sudo yum install stress -y
(if you get error, try following command before the stress install command : sudo amazon-linux-extras install epel -y)
Put load on ec2 using following command : sudo stress --cpu 12 --timeout 240s
To set alarm, run following command in aws cloudshell:
aws cloudwatch set-alarm-state --alarm-name CPUUtilzationForTG --state-value ALARM --state-reason "test"
AWS Application Load Balancer setup with target group EC2 : • AWS Application Load B...
AWS CodePipeline : • AWS CodePipeline with ...
AWS Lambda Hand-On Playlist : • AWS Lambda
AWS CloudFormation : • AWS CloudFormation
Subscribe on : / @kodedge
If you like the video please subscribe and comment.
----------------------------------
Disclaimer/Policy:
- Video is intended for educational purposes only and explanations about technical topics.
- We make every effort to ensure the accuracy of the information presented, but we cannot guarantee that all information is current or entirely free from errors.
- Viewers are encouraged to exercise their own judgment and consider their unique circumstances when applying the information from this video.
- Mention of specific products, services, or brands in this video does not constitute an endorsement unless otherwise specified.
- By accessing and using the information presented in this video, viewers agree to do so at their own risk, and we shall not be liable for any damages or losses.
- All logos and images used in this video are the property of their respective copyright holders. Any copyrighted material is used here for educational purposes only.
- Our use of logos and images is not intended to challenge or infringe upon the rights of the copyright holders, and we acknowledge their ownership
- The inclusion of logos and images is for non-commercial, educational purposes only.
#awstutorial #autoscaling #autoscalingpolicy #kodedge
Userdata Script :
#!/bin/bash
yum update -y
yum install -y httpd
systemctl start httpd
systemctl enable httpd
echo "This message from : $(hostname -i)" > /var/www/html/index.html
Excellent Tutorial Bro . Very Simplification For Understanding Concept And Practice Too.
Thanks for the feedback
Thanks for exceptional diagram (AWS ALB with EC2 Auto Scaling). Subscribed.
Thanks for the feedback
This tutorial was very good, pls do more videos on AWS.
Thanks for the feedback. Yes it’s in progress. Please let me know on which topics you are interested.
EKS, and ECS.
Here is the tutorial on EKS : ruclips.net/video/aXOB4tR0ONU/видео.html and on ECS : ruclips.net/video/ARGmrYFfv44/видео.html
Thanks
Thanks for the feedback.
Brilliant Video Mate
Thanks for the feedback
sudo yum install -y
SUPERB CLASS
Thanks for the feedback
aws cloudwatch set-alarm-state --alarm-name "name of your alarm" --state-value ALARM --state-reason "test
I have a question,
What was the purpose of,
" aws cloudwatch set-alarm-state --alarm-name CPUUtilizationForTG --state-value ALARM --state-reason "test" "
this command.
What if we do it by increasing the stress?
Simply neet explaination ELB & ASG and what application that you
used for this slid presentaion?
Thanks for the feedback. I am using keynote for the slides.
Good explanation ❤❤ just one doubt.. If we have 2 ec2 instance in asg and we put load on only one ec2 instance then how cloud watch metric will capture cpu utilization??? Will it be average of both ec2 or it will capture individual load???
Thanks for the feedback.
When you have an Auto Scaling group with multiple EC2 instances, the CPU utilization metric reported to CloudWatch will be an average across all instances in the Auto Scaling group.
If you put load on only one EC2 instance, CloudWatch will still capture the CPU utilization for that instance, but when you view the metric for the Auto Scaling group as a whole, it will be an average of the CPU utilization across all instances in the group.
So, if you put load on only one EC2 instance, that instance's CPU utilization will increase, but the overall average CPU utilization for the Auto Scaling group might not reach the threshold for scaling out unless the other instance(s) also have high CPU utilization or contribute to the average.
For detail information please refer this documentation : docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-target-tracking.html
docs.aws.amazon.com/autoscaling/application/userguide/target-tracking-scaling-policy-overview.html
Bro it showing it works!
New created ec2 hasn't any application why?
It have httpd server with sample html.
Hi brother, my ALB DNS is not working, what may be the reasons
Check security group. What is the exact issue you are getting.
@@kodedge getting "502 GATEWAY ERROR"
Hi, Check the security groups of both ALB and AutoScaling group.
If proper traffic allowed as shown in the video.
Possibly check here as well at : 16:46 in the video.
Still if not works try these troubleshooting points:
docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html#http-502-issues
repost.aws/knowledge-center/elb-alb-troubleshoot-502-errors
I am getting 502 error aftrer loading alb dns name
docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html
Bhai tumse kuch puchna tha
Yes
Isn`t the alarm should be triggered automatically when the desired count is set from 2 to 1? Do we need to manually trigger the alarm referring ruclips.net/video/c4DeyLesQr8/видео.html
We have created alarm for cpu utilisation. When cpu utilisation goes above specified threshold then only alarm will get triggered. Can you elaborate for which alarm you are talking about.
I think desired state works only then asg initially spin up ec2.. Once done... It will work on minsize