The Overall "AWS" Part 4:- AWS "CloudWatch" Service 2

A Climax Part Of AWS CloudWatch:-

AWS CloudWatch Service is very important service in each level. If user use AWS console for practice purpose, user use AWS console to their Private project management purpose and a organization use to manage their data with AWS Console everyone used AWS CloudWatch Service For Monitoring and Management Purpose. In Last blog We cover the things which is Details of AWS CloudWatch, Activities, Services, Benifits of AWS CloudWatch. But the main thing of AWS CloudWatch is we can set alarm for us for any situation occur. It's
fully customisable with user defined policies. Now in this blog we  learn on which service we enable a alarm policy and Step of setting an alarm.
In AWS there are 7 mainly services which used mainly on every project of AWS. Its not necessary to used all this Services on every project but some of them are must.
We can view our alarm statistics with this 7 services. We can say it's a 7 service package bundle to manage the alarm statistics for their different services.
We can studied each of that service deeply in next several blogs. But for learning how to use CloudWatch alarm service we have to learn this 7 service usage before. Here just a small intro of that services:-
1) EBS(Elastic Block Storage):- It is high performance block storage service working with AWS EC2 service to provide a block storage facility at any level of scale.
2)EFS(Elastic File System):- It Provide fully managed, simple and scalable elastic NFS file system to provide a service for cloud application and on-premises environment. It also providea scale  on demand petyabyte  of data without disrupting  the data.
3) ElasticBeanstalk:- It Provide a facility to uploading any type of web application which services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS.
4) S3:- S3 bucket is storage facility where we drop a data which we have to show as an website content. Its an object storage service where we can drop any amount of data with data Availability, high performance and security.
5) EC2:- We can call in simple language for EC2 is a Virtual machine. EC2 is a service where we can deploy any server side Operating system with various computing resources facility which are some free tier eligible or some are paid as per service requirement.
6) ELB:- It distributed a incoming traffic load of application which deploy on AWS console in various load balancer targets.
7) RDS:- It is used to Deploy, Operate a Relational Database in the Cloud Platform.
This is  a simple and nominal explanation of 7  services Now we move to set up an alarm. Following are the steps to set a alarm for EC2 service.
Here the theotical explainTion is to confusion to set an alarm.
Link for practical Demo to set an alarm from Random YouTube channel Available Video link- Practical Demo Of Setup an alarm on CloudWatch
For set an alarm you must choose an instance Id. For instance Id we have to create and  Instance from EC2 service.
Here I attach a link of setup an EC2 instance for your instance Id purpose.
We cover a EC2 topic in depth in next upcoming blogs. Here is link:-

 Practical Demo EC2 service Installation

So now we learn how to check the alarm setting is properly or not and some further attributes of Set an alarm policy Such as:-
Metric Alarm States
A metric alarm has the following possible states:
OK – The metric or expression is within the defined threshold.
ALARM – The metric or expression is outside of the defined threshold.
INSUFFICIENT_DATA – The alarm has just started, the metric is not available, or not
enough data is available for the metric to determine the alarm state.
Evaluating an Alarm
When you create an alarm, you specify three settings to enable CloudWatch to evaluate when to change the alarm state:
Period is the length of time to evaluate the metric or expression to create each
individual data point for an alarm. It is expressed in seconds. If you choose one minute
as the period, there is one data point every minute.
Evaluation Period is the number of the most recent periods, or data points, to evaluate
when determining alarm state.
Datapoints to Alarm is the number of data points within the evaluation period that must be breaching to cause the alarm to go to the ALARM state. The breaching datapoints don't have to be consecutive, they just must all be within the last number of data points equal to Evaluation Period.
Here We cover all the methodologies of AWS CloudWatch Services.
Thanks for Reading. Hope you like it.