It really takes a lot of time to make videos with designs but would never compromise on the quality, because I make these videos for you and you should always get the best. Please support the channel by liking the video and subscribing. Happy New Year 2021.
I'm taken by this. I had the privilege of reading something similar, and I was truly taken by it. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
This is a top-notch channel for AWS cloud learning - period. Great explanation, High quality content and tackles real-time scenarios. This channel deserves more subscribers.
Thank you for the detailed video on cloudwatch. some times even the most basic things will make sense and click to us during architecture designing if we go through it clearly and concisely. Kudos!
Do you have any video or guidance to understand the existing architecture. For an example, how to know what does the EC2 instance do and how are they connected
Hi, The explanation of concepts is exceptional and very helpful but it would be great if you can provide a hands-on lab on AWS console level for the topic thought in the video. Thank you😊
Thank you, best explanation of CloudWatch on UA-cam! Can you please explain the difference between using autoscaling groups vs using CloudWatch Events to scale EC2 instances? Are there 2 different ways (through ASG and CloudWatch) to implement autoscaling?
condition: if i have launched 2 ec2 with the help of autoscaling group. and now i want autoscaling group to launch one more ec2 if there is more than 50% cpu utilization on only one ec2. and also to set alarm for cpu utilization so what changes do i have to make in alarm so that if i only increase cpu utilization on one ec2 out of 2 then 1 more instance will be launched?
To achieve this, you'll need to create a CloudWatch alarm that monitors CPU utilization and then configure the Auto Scaling group to respond to that alarm. Here's a step-by-step guide: Create a CloudWatch Alarm: a. Sign in to the AWS Management Console, and open the CloudWatch console at console.aws.amazon.com/cloudwatch/. b. In the navigation pane, click on "Alarms," then "Create alarm." c. Click on "Select metric," then choose the "EC2" namespace and select the "Per-Instance Metrics" tab. d. Select the "CPUUtilization" metric, and then click "Select metric." e. Configure the alarm settings: Name: Provide a unique name for the alarm. Description (optional): A brief description of the alarm. "Whenever" condition: Select "CPUUtilization" and set the condition to "GreaterThanOrEqualToThreshold" with a value of 50. "For at least" field: Set the consecutive periods and duration for which the alarm should be triggered (e.g., 1 period of 1 minute). "Actions" section: Under "Auto Scaling action", select "Add action" and choose "Scale out" and then select the relevant Auto Scaling group. f. Click "Create Alarm." Configure the Auto Scaling group: a. Open the Amazon EC2 console at console.aws.amazon.com/ec2/. b. In the navigation pane, click on "Auto Scaling groups." c. Select the Auto Scaling group you want to modify, and click on the "Scaling policies" tab. d. Click on "Create scaling policy" and select "Step scaling policy" or "Target tracking policy" based on your preference. e. Configure the policy settings as needed, making sure to associate the CloudWatch alarm you created in step 1. Now, when the CloudWatch alarm is triggered (CPU utilization is above 50% on any single instance), the Auto Scaling group will launch an additional EC2 instance. Note that this setup may not be ideal for all situations, as it can lead to unnecessary scaling if only one instance is experiencing high CPU utilization while the other instance(s) remain idle. Consider your specific use case and load distribution requirements when implementing this solution.
@@Pythoholic did this already but didn't work..i had to increased cpu utilization on both ec2..but the thing is i want to increase utilization of only one ec2 and want to see if auto scaling group will launch 3rd ec2 or not?
The issue here is that by default, CloudWatch alarms for EC2 instances are aggregated across instances within an Auto Scaling group. When you create an alarm based on the "CPUUtilization" metric, it's actually monitoring the average CPU utilization across all instances in the group. To achieve the desired behavior of launching a new instance when any single instance has a CPU utilization greater than 50%, you can use a custom CloudWatch metric that records the maximum CPU utilization of any instance in the Auto Scaling group.
Hello Quick: Scenario CloudWatch alarm/metric pointing to a Stream log file pattern: "ERROR" period: 30 minutes. Alarm got into state: In Alarm, and sends a event to SNS to received an email from the alarm state, When consecutive state of alarm I am just getting one single alarm. Is there a way to configure alarm to get 2 or 3 different emails if Alarm state continue with the same In-Alarm state as many as consecutive iteration?
Amazon CloudWatch Alarms are designed to send notifications when they change state. By default, they do not continue to send notifications for every evaluation period that the alarm remains in the same state. If an alarm stays in the `ALARM` state over multiple periods, it does not send multiple notifications. However, there are a few workarounds to achieve what you want: 1. **Use AWS Step Functions or AWS Lambda:** You can create a Step Function or Lambda function that triggers on the CloudWatch alarm's SNS message. This function could then be set to send additional emails at your desired interval until the alarm state is cleared. Note, this requires additional setup and management. 2. **Create more alarms with different thresholds or periods:** You could create additional alarms with slightly different thresholds or periods. This isn't an ideal solution because it might cause some false positives, but it would give you multiple notifications. 3. **Metric Math Alarm:** If your use case allows, you can use metric math expressions to create an alarm. For example, you can create an alarm that triggers when the sum of errors over the last three periods exceeds a certain threshold. 4. **Using third-party services:** You could consider using a third-party service that offers more advanced alerting options than CloudWatch. These services often have features to customize alerts and notifications in a more granular way. Remember, it's important to manage and keep track of these notifications to avoid noise and ensure that the important alerts are not missed.
It really takes a lot of time to make videos with designs but would never compromise on the quality, because I make these videos for you and you should always get the best. Please support the channel by liking the video and subscribing. Happy New Year 2021.
1
These videos are helping us much. We really appreciate your hard work and dedication, Thanks a lot!
Really awesome video. Could you please let me know which tool do you use to create diagrams.
Just ppt thanks much
This video is far better than the course that I purchased on udemy
Thank u ashwath for supporting. Please do share with your friends it really helps
I'm taken by this. I had the privilege of reading something similar, and I was truly taken by it. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
Awesome content. Better than many paid content. Highly appreciate your effort.
This is a top-notch channel for AWS cloud learning - period. Great explanation, High quality content and tackles real-time scenarios. This channel deserves more subscribers.
Thanks for the support. Please spread the word. Helps a lot
It was worth it for sure. I am preping for AWS CA exam. Hope this should help me in passing exam and also implement some solutions
This is really good. He takes time to give details and visualization for good understanding. Great jobs. Thanks.
Hi, very nicely explained, animations are the key which makes to understand easily, many thanks for sharing.
Thanks rekha
This is really high-quality stuff that I have loved watching and learning. Thanks once again for this wonderful animated video.
Thank you for the detailed video on cloudwatch. some times even the most basic things will make sense and click to us during architecture designing if we go through it clearly and concisely. Kudos!
This really a very informative course. Your course is helping me understand the detailed concepts of cloud. Thanks for all the efforts.
thanks bhavana
all the best
Thank you so much for all the efforts you've put in to create these very informative videos
thanks anju
You are the best tutor😊
Thanks a lot Mahesh 🙏
Excellent Session!
Really good one... Visually so beautiful one👍
Amazing video not this , all your video are Great to watch , Many Thanks
very well explained, thank you sir .
Thanks 😊
Really good content with unique methodology
Brother really great thanks please do more videos on premises
My man! Thank you!
Great videos man...Thank you for taking time to make these.
Thanks for the video, 😊
A request, please start your videos with some questions that are asked in AWS certification.
Sure 😃 thanks for the feedback
Very well explained! But if you are using Kubernetes, the setup will change vastly!
great Video ! thank you
Do you have any video or guidance to understand the existing architecture. For an example, how to know what does the EC2 instance do and how are they connected
Hi, please refer the link for the playlist of the course. I have a lot of videos on EC2.
I hope that would help
Great video
Hi, The explanation of concepts is exceptional and very helpful but it would be great if you can provide a hands-on lab on AWS console level for the topic thought in the video. Thank you😊
Thanks a lot for the feedback.
Thank you, best explanation of CloudWatch on UA-cam!
Can you please explain the difference between using autoscaling groups vs using CloudWatch Events to scale EC2 instances? Are there 2 different ways (through ASG and CloudWatch) to implement autoscaling?
Sure !!
Your content and videos are amazing. If you don't mind can you tell which software you use to create these fascinating videos?
Thanks bro.. it's just PowerPoint and it's Animation
Awesome content. I subscribed your channel.
condition: if i have launched 2 ec2 with the help of autoscaling group. and now i want autoscaling group to launch one more ec2 if there is more than 50% cpu utilization on only one ec2. and also to set alarm for cpu utilization so what changes do i have to make in alarm so that if i only increase cpu utilization on one ec2 out of 2 then 1 more instance will be launched?
To achieve this, you'll need to create a CloudWatch alarm that monitors CPU utilization and then configure the Auto Scaling group to respond to that alarm. Here's a step-by-step guide:
Create a CloudWatch Alarm:
a. Sign in to the AWS Management Console, and open the CloudWatch console at console.aws.amazon.com/cloudwatch/.
b. In the navigation pane, click on "Alarms," then "Create alarm."
c. Click on "Select metric," then choose the "EC2" namespace and select the "Per-Instance Metrics" tab.
d. Select the "CPUUtilization" metric, and then click "Select metric."
e. Configure the alarm settings:
Name: Provide a unique name for the alarm.
Description (optional): A brief description of the alarm.
"Whenever" condition: Select "CPUUtilization" and set the condition to "GreaterThanOrEqualToThreshold" with a value of 50.
"For at least" field: Set the consecutive periods and duration for which the alarm should be triggered (e.g., 1 period of 1 minute).
"Actions" section: Under "Auto Scaling action", select "Add action" and choose "Scale out" and then select the relevant Auto Scaling group.
f. Click "Create Alarm."
Configure the Auto Scaling group:
a. Open the Amazon EC2 console at console.aws.amazon.com/ec2/.
b. In the navigation pane, click on "Auto Scaling groups."
c. Select the Auto Scaling group you want to modify, and click on the "Scaling policies" tab.
d. Click on "Create scaling policy" and select "Step scaling policy" or "Target tracking policy" based on your preference.
e. Configure the policy settings as needed, making sure to associate the CloudWatch alarm you created in step 1.
Now, when the CloudWatch alarm is triggered (CPU utilization is above 50% on any single instance), the Auto Scaling group will launch an additional EC2 instance. Note that this setup may not be ideal for all situations, as it can lead to unnecessary scaling if only one instance is experiencing high CPU utilization while the other instance(s) remain idle. Consider your specific use case and load distribution requirements when implementing this solution.
@@Pythoholic did this already but didn't work..i had to increased cpu utilization on both ec2..but the thing is i want to increase utilization of only one ec2 and want to see if auto scaling group will launch 3rd ec2 or not?
The issue here is that by default, CloudWatch alarms for EC2 instances are aggregated across instances within an Auto Scaling group. When you create an alarm based on the "CPUUtilization" metric, it's actually monitoring the average CPU utilization across all instances in the group.
To achieve the desired behavior of launching a new instance when any single instance has a CPU utilization greater than 50%, you can use a custom CloudWatch metric that records the maximum CPU utilization of any instance in the Auto Scaling group.
@@Pythoholic okay i"ll try and will tell u..thanks for the guidance bdw
Hello Quick: Scenario CloudWatch alarm/metric pointing to a Stream log file pattern: "ERROR" period: 30 minutes. Alarm got into state: In Alarm, and sends a event to SNS to received an email from the alarm state, When consecutive state of alarm I am just getting one single alarm. Is there a way to configure alarm to get 2 or 3 different emails if Alarm state continue with the same In-Alarm state as many as consecutive iteration?
Amazon CloudWatch Alarms are designed to send notifications when they change state. By default, they do not continue to send notifications for every evaluation period that the alarm remains in the same state. If an alarm stays in the `ALARM` state over multiple periods, it does not send multiple notifications.
However, there are a few workarounds to achieve what you want:
1. **Use AWS Step Functions or AWS Lambda:** You can create a Step Function or Lambda function that triggers on the CloudWatch alarm's SNS message. This function could then be set to send additional emails at your desired interval until the alarm state is cleared. Note, this requires additional setup and management.
2. **Create more alarms with different thresholds or periods:** You could create additional alarms with slightly different thresholds or periods. This isn't an ideal solution because it might cause some false positives, but it would give you multiple notifications.
3. **Metric Math Alarm:** If your use case allows, you can use metric math expressions to create an alarm. For example, you can create an alarm that triggers when the sum of errors over the last three periods exceeds a certain threshold.
4. **Using third-party services:** You could consider using a third-party service that offers more advanced alerting options than CloudWatch. These services often have features to customize alerts and notifications in a more granular way.
Remember, it's important to manage and keep track of these notifications to avoid noise and ensure that the important alerts are not missed.
Please make video on Prometheus and Grafana.
bro plz dont think dat m criticizing u m ur wellwisher ur voice d way u r teaching all things r gud but i think dat u have to improve this topic
thanks bro i am all in for feedback
where can i find the demo, is it available?
the next video on that playlist is the demo
Hi .. Can you do EKS and ECR videos
How do u create these beautiful 😍 animations?
its powerpoint
plz make another video on cloud watch with lab in hindi yahan kuch smjh nhi ara half video k bd jo b u r saying
Please speak little bit slow so we can understand more
Thanks nadeem for the feedback, point taken.
Bruh, there is a playback speed control just meant for this. Come on now 😄
A