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

Monitoring Step Functions using CloudWatch alarms

When you have a step-by-step workflow and you need to coordinate it using a service, then AWS Step Functions is the service for that. Step Functions makes it easy for non-engineers to be able to set up a step-by-step workflow using a state machine. Say, for example, you want to create a flow that receives customer information, sifts through the data and collects emails, and sends feedback to the customer based on information found in the biodata. Let's assume we want to find out whether a customer's age is eligible for the service. This is a flow that has four stages:

  1. Collect customer/user information.
  2. Get the email from the customer data.
  3. Check for information about the age of the customer to see whether it is over the eligible age.
  4. Send back an email notifying the customer of whether they are eligible or not.

This is a step-by-step workflow of being able to filter those who are eligible for a...