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

Orchestrating container services in AWS

The introduction was more about understanding the basics of containers and the advantages of containers over VMs. Moving forward, let's look at the concept of container orchestration. When an application is packaged as a Docker image, for the purposes of running it as a container, it is quite easy to manage, deploy, and monitor when it is just a single container or a few containers running in a single VM. But as these containers increase, say from 1 to 10 to 15, it becomes more difficult and complicated to manage, deploy, scale, and even monitor that number of containers. Moreover, containers require high availability when the application is in production (customer-facing), hence there should be a more automated way to manage these operations that is more flexible and easier to manage. This is where container orchestration comes in. Without a container orchestration tool, it is quite difficult to perform all the necessary operational tasks...