you folks are amazing !!. I really really appreciate for your time sharing your knowledge has so much humanity in it. teaching every one free. your are very much appreciated on my part !!
@ccm590 Жыл бұрын
this is not Pytholic, it is alcoholic...I am addicted bro
@ccm590 Жыл бұрын
a BIG heart for you bro
@vigilkumarap3 жыл бұрын
@pythoholic: Thanks to ur channel, was able to get my basics clear and clear the exam yesterday.
@Pythoholic3 жыл бұрын
Awesome news,,, congratulations 👍 please help the channel if u wish to by posting ur accomplishment on linked in and tagging the channel. Many congratulations
@honoratob.felicitasjr.7529 Жыл бұрын
Thank you for this video. I was able to create a CPU alarm for Redshift for the first time. :)
@matrixtoogood56013 жыл бұрын
Amazing explanation, your channel will become very popular for all AWS certifications in a few years!
@pannalal39943 жыл бұрын
pls share these wonderful piece of knowledge n effort which will keep motivated the teacher...
@amritasingh11053 жыл бұрын
Nice tutorial with clear explanation 👌
@SravyaTirumala Жыл бұрын
Thankyou for the video. It was so clear and have understood clearly.
@TechJedi0076 ай бұрын
Not sure why, but I created the alarm, created a topic, and subscribed to the topic. I'm still unable to get any notifications even though the metrics I set were really low after running the stress test.
@ShadabAnsari-rc7cz3 жыл бұрын
very good and informative lecture. u r rocking man.
@joeldjomou40713 жыл бұрын
Awesome video man!!! Thank you for the good work.
@kaboodlefish Жыл бұрын
Is there a way to prevent ec2s from contributing to metrics until x minutes after they've started? I'm deploying via terraform, so my cpu alarm is sounding whenever an ec2 starts as it's obviously using a lot during that initial period.
@Pythoholic Жыл бұрын
Yes, you can prevent newly launched EC2 instances from contributing to metrics until a certain amount of time has passed after their start. One way to achieve this is by using a combination of AWS CloudWatch Alarms and Auto Scaling Lifecycle Hooks. Here's a high-level overview of the process: 1. **CloudWatch Alarm**: Create a CloudWatch alarm to monitor the CPU usage of your EC2 instances. This alarm will be triggered when the CPU usage exceeds a certain threshold. 2. **Auto Scaling Group (ASG) Configuration**: Ensure that your EC2 instances are launched within an Auto Scaling Group (ASG). The ASG is responsible for maintaining the desired number of instances and automatically launching or terminating instances based on your defined policies. 3. **Lifecycle Hook**: Create an Auto Scaling Lifecycle Hook that pauses the EC2 instance when it's launched. A lifecycle hook allows you to perform custom actions as instances launch or terminate within the ASG. 4. **Pause EC2 Instance**: When the EC2 instance is launched, the lifecycle hook will be triggered, and the instance will be in a "wait" state. During this time, you can implement a script or mechanism on the instance to prevent metrics reporting (such as disabling CloudWatch agent or other monitoring tools). 5. **Delayed Metric Contribution**: After a specified amount of time (e.g., x minutes), you can have your custom script or mechanism enable monitoring tools and allow the instance to start contributing to metrics. At this point, the lifecycle hook can complete, and the instance will be fully operational. By using this approach, you can avoid false alarms for high CPU usage during the initial period after launching EC2 instances. Keep in mind that you will need to handle the lifecycle hook logic in your EC2 instance's userdata or launch script. You can use AWS SDKs or CLI commands in your userdata script to interact with Auto Scaling and signal when the instance is ready to start contributing to metrics. Implementing this solution requires some scripting and configuration work, but it can be a useful way to prevent alarms from triggering unnecessarily during the initial period after launching EC2 instances.
@bibifedomatova2115 Жыл бұрын
while creating ec2 why did you use one of your own subnet instead of default one. is there any purpose behind this? Your demos and graphic demonstration is on another level. thank you! its educational and fun!
@Pythoholic Жыл бұрын
Yes its because we wanted to host it on our network ie the one we created to test it.
@leovillaz Жыл бұрын
I´m trying to configure Cloudwatch to monitor CPU utilization per thread but I only catch CPU utilization average. I would like to know if it is possible to configure Cloudwatch to monitor each of the CPU threads individually, as MSSQL runs on the server, which is configured to use 6 of the 8 available threads. I looked through various AWS documentation and none, in particular, told me how to configure Cloudwatch for this. And even using the Cloudwatch Agent I couldn't get the expected result.
@Pythoholic Жыл бұрын
Have you tried cloud watch metric "ThreadUtilization" did that help: cloudwatch = boto3.client('cloudwatch') # Define the metric data metric_data = [ { 'MetricName': 'ThreadUtilization', 'Dimensions': [ { 'Name': 'InstanceId', 'Value': 'i-1234567890abcdef0' }, { 'Name': 'ThreadId', 'Value': '1' }, ],
@diptidahat1141 Жыл бұрын
How do I create a CloudWatch alarm for CPU Utilization metric for multiple instances? It lets you select just one instance while creating an alarm but I want to add multiple instances.
@Pythoholic Жыл бұрын
You can refer to composite alarms : docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Composite_Alarm.html But can you please share your requirement, in what condition do u plan to monitor multiple instance for one value
@vinothkumarak8880 Жыл бұрын
I have a query, if want create alarm by single metric itself for high cpu utilization more than one instances? if is possible, please help me on this.
@Pythoholic Жыл бұрын
Yes, it is possible to create an alarm based on a single metric for high CPU utilization across more than one instance. This process will largely depend on the system or service that you are using to monitor your instances, such as AWS CloudWatch, Google Cloud Monitoring, or some other monitoring service. Here's a general outline of how to do it in AWS CloudWatch: 1. **Create a new Alarm:** In the CloudWatch console, navigate to Alarms and click on "Create Alarm." 2. **Select a Metric:** Search for and select the `CPUUtilization` metric associated with your instances. If your instances are part of an Auto Scaling group, you can use the `CPUUtilization` metric associated with the Auto Scaling group. 3. **Define the Alarm condition:** You'll need to specify the threshold for the alarm. For high CPU utilization, you might set this at 80%, for example, but the exact figure will depend on your requirements. 4. **Configure Actions:** Define what action should be taken when the alarm state is triggered. This could be sending a notification, triggering an Auto Scaling action, etc. 5. **Add a Name and Description:** Give your alarm a name and a description so you can easily identify it later. 6. **Create the Alarm:** Finally, review your settings and create the alarm. This is a very basic example and the exact steps can vary based on your specific requirements and the monitoring service you are using. Please let me know if you need help with a specific monitoring service or if you have more detailed requirements.
@saeedshaikh4369 Жыл бұрын
I have EKS cluster and would like monitor all EC2 instance under that , how to achieve this without applying separate alarm on each instance
@Pythoholic Жыл бұрын
docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/deploy-container-insights-EKS.html This can help you setup insight for EKS cluster.
@Citypoint8882 жыл бұрын
Thanks for the awesome video. You are the best.
@ganeshwankhede33293 жыл бұрын
For connecting to EC2, which UI tool you are using ? alternative to Putty ?
@Pythoholic3 жыл бұрын
Termius .. i have a video where i have shown how to use it Mobaxterm Putty Termius please check that
@ganeshwankhede33293 жыл бұрын
@@Pythoholic thanks
@HA042592 жыл бұрын
Nice explanation.. when states will change Alaram to OK and OK to Alaram?
@Pythoholic2 жыл бұрын
When the condition are met for the trigger of the alarm
@yadikierukulareddy32803 жыл бұрын
Hi , Cant we create a single alarm for metric of cpu utilisation for couple of ec2 instances ?
@Pythoholic3 жыл бұрын
Why not? Yes you can
@m.vineeth97243 жыл бұрын
Which software did you use for connecting to the EC2 instance ?
@Pythoholic3 жыл бұрын
Termius.. I have a video explaining how to use it as well.
@m.vineeth97243 жыл бұрын
@@Pythoholic Thanks a lot, I ll definitely go through that video.
@p1xedge3 жыл бұрын
please upload video how to set alarm in cloudwatch and scale ec2 instance as load increases and send sns notification using python boto3
@Pythoholic3 жыл бұрын
Sure
@brucewayne-bv4ok2 жыл бұрын
Hey small doubt why did u keep 0.6 as threshold does that mean if cpu utiliZation is above 60 % u will be notified ??
@Pythoholic2 жыл бұрын
Yes that was just for a demo purpose you can change it as per your requirement
@brucewayne-bv4ok2 жыл бұрын
@@Pythoholic so do I have to keep it 75% if I want to get notified if cpu utilisation crosses 75%??
@Pythoholic2 жыл бұрын
yes and based on that number of thresholds you keep , for example it may be like 3 times then once it crosses for 3 times then it will notify
@brucewayne-bv4ok2 жыл бұрын
@@Pythoholic hey one more thing !! what about the average , sum , max and min !! do they play a factor ?? am keeping avg jst like u did
@Pythoholic2 жыл бұрын
you can read this it would take be easier for understanding docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Statistics-definitions.html
@rohithreddykatta86142 жыл бұрын
We have around 50 lambda function’s and for them we have to setup “Errors” metric cloud watch alarms. Looking for automation options.
@Pythoholic2 жыл бұрын
terraform is the way
@byronmedina6150 Жыл бұрын
funciona webillo 10/10
@samitingole8672 Жыл бұрын
which software use for cannet ec2 insta
@Pythoholic Жыл бұрын
Putty mobaxterm for windows Ssh for Linux
@gungunsingh72743 жыл бұрын
Thank you sir
@vinothkumarak8880 Жыл бұрын
same @dipti dahat asked the query, that could you please clarify me.
@sharukhshaikh83553 жыл бұрын
With what else we can do monitorining
@Pythoholic3 жыл бұрын
Monitoring, Alert, Reporting, Dashboards, Event based notification and automation.
@uploadvoice2 жыл бұрын
Kibana (ELK stack)
@manoraja93563 жыл бұрын
Please do on events
@abalilziad444410 ай бұрын
Hello , do you have a udemy courses ?
@Pythoholic9 ай бұрын
Hi I am working on the udemy course will update on the channel once done. Thanks for the feedback