Wonderfull tutorial, First explained the whole theory properly, so that you'll have context of everything, Then, moved to practical, so everything studied in the theory made sense! Thanks a lot!!
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
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
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 ua-cam.com/video/c4DeyLesQr8/v-deo.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.
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
Wonderfull tutorial,
First explained the whole theory properly, so that you'll have context of everything,
Then, moved to practical, so everything studied in the theory made sense!
Thanks a lot!!
Thanks for the feedback.
Excellent Tutorial Bro . Very Simplification For Understanding Concept And Practice Too.
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 : ua-cam.com/video/aXOB4tR0ONU/v-deo.html and on ECS : ua-cam.com/video/ARGmrYFfv44/v-deo.html
Thanks for exceptional diagram (AWS ALB with EC2 Auto Scaling). Subscribed.
Thanks for the feedback
Brilliant Video Mate
Thanks for the feedback
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
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
Bro it showing it works!
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
Thanks
Thanks for the feedback.
New created ec2 hasn't any application why?
It have httpd server with sample html.
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 ua-cam.com/video/c4DeyLesQr8/v-deo.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