Book Image

AWS Observability Handbook

By : Phani Kumar Lingamallu, Fabio Braga de Oliveira
Book Image

AWS Observability Handbook

By: Phani Kumar Lingamallu, Fabio Braga de Oliveira

Overview of this book

As modern application architecture grows increasingly complex, identifying potential points of failure and measuring end user satisfaction, in addition to monitoring application availability, is key. This book helps you explore AWS observability tools that provide end-to-end visibility, enabling quick identification of performance bottlenecks in distributed applications. You’ll gain a holistic view of monitoring and observability on AWS, starting from observability basics using Amazon CloudWatch and AWS X-Ray to advanced ML-powered tools such as AWS DevOps Guru. As you progress, you'll learn about AWS-managed open source services such as AWS Distro for OpenTelemetry (ADOT) and AWS managed Prometheus, Grafana, and the ELK Stack. You’ll implement observability in EC2 instances, containers, Kubernetes, and serverless apps and grasp UX monitoring. With a fair mix of concepts and examples, this book helps you gain hands-on experience in implementing end-to-end AWS observability in your applications and navigating and troubleshooting performance issues with the help of use cases. You'll also learn best practices and guidelines, such as how observability relates to the Well-Architected Framework. By the end of this AWS book, you’ll be able to implement observability and monitoring in your apps using AWS’ native and managed open source tools in real-world scenarios.
Table of Contents (22 chapters)
1
Part 1: Getting Started with Observability on AWS
6
Part 2: Automated and Machine Learning-Powered Observability on AWS
11
Part 3: Open Source Managed Services on AWS
15
Part 4: Scaled Observability and Beyond

Observability best practices at scale

An organization may adopt a multi-account and multi-Region strategy to improve security, manage costs, comply with regulations, prepare for disaster recovery, reduce latency, and improve performance. By creating separate accounts for different parts of the organization, sensitive data can be isolated, reducing the risk of a data breach and improving security. A multi-Region strategy helps organizations meet compliance requirements and ensure business continuity in the event of an outage or disaster. This strategy also helps to minimize the impact or blast radius of any potential security incidents or failures by limiting their scope to a specific account or Region. Let’s look at the common deployment model of applications in multi-account, multi-Region topologies and how organizations manage them.

Understanding multi-account and multi-Region topologies

Let’s have a look at how multi-account and multi-Region topologies are created...