Book Image

Infrastructure Monitoring with Amazon CloudWatch

By : Ewere Diagboya
Book Image

Infrastructure Monitoring with Amazon CloudWatch

By: Ewere Diagboya

Overview of this book

CloudWatch is Amazon’s monitoring and observability service, designed to help those in the IT industry who are interested in optimizing resource utilization, visualizing operational health, and eventually increasing infrastructure performance. This book helps IT administrators, DevOps engineers, network engineers, and solutions architects to make optimum use of this cloud service for effective infrastructure productivity. You’ll start with a brief introduction to monitoring and Amazon CloudWatch and its core functionalities. Next, you’ll get to grips with CloudWatch features and their usability. Once the book has helped you develop your foundational knowledge of CloudWatch, you’ll be able to build your practical skills in monitoring and alerting various Amazon Web Services, such as EC2, EBS, RDS, ECS, EKS, DynamoDB, AWS Lambda, and ELB, with the help of real-world use cases. As you progress, you'll also learn how to use CloudWatch to detect anomalous behavior, set alarms, visualize logs and metrics, define automated actions, and rapidly troubleshoot issues. Finally, the book will take you through monitoring AWS billing and costs. By the end of this book, you'll be capable of making decisions that enhance your infrastructure performance and maintain it at its peak.
Table of Contents (16 chapters)
Section 1: Introduction to Monitoring and Amazon CloudWatch
Section 2: AWS Services and Amazon CloudWatch

Configuring a basic CloudWatch event

Let's take a real-life scenario of how CloudWatch Events can be quite important to use for a very simple solution. Let's assume that an organization, MCS Consulting, owns a bunch of staging servers used as EC2 instances. These servers are not used for 24 hours and are only used when the developers need to run application tests. This means that running the server just within the working hours, that is, between 9 a.m. to 5 p.m. or 6 p.m., is how much is needed for useful purposes. This means that between 6.01 p.m. and 8.59 a.m., the EC2 instance(s) can be shut down, which will result in some huge cost savings for running those instances. This configuration can be done using CloudWatch Events. For this to work, we need the instance ID(s) of the EC2 instance we wish to place on this schedule. Let's assume the instance ID is i-1234567890abcdef0.

For this setup, we will not be using the event pattern; instead, we will be going through...