This Guidance helps you implement the observability capability in your cloud environment. Observability enables you to gather and analyze operational data about system and application activities. This includes the analysis of data to identify anomalies, indicators of compromise, performance, and configuration changes. Building observability into your cloud foundation will help you establish a reliable, secure, and scalable environment to deploy, operate, and govern your cloud workloads.
Please note: [Disclaimer]
Build CloudWatch metrics to filter and alert based on key performance indicators and operational events.
Build and share dashboards and visualizations using CloudWatch, and set up CloudWatch alarms that notify you when resources reach a pre-defined threshold.
Centralize persistent long-term log storage for CloudWatch logs, CloudTrail logs, and AWS Config logs to manage lifecycle and cost optimization.
Implement automated log archival by exporting CloudWatch logs to a centralized Amazon Simple Storage Service (Amazon S3) bucket.
Centralize operational and security events across your AWS Organization by using EventBridge and EventBridge rules.
Establishing observability across your cloud foundation helps you gain real-time insights into resource performance and various aspects of your cloud environment, including resource utilization, network traffic, application performance, and security events.
This visibility into your cloud operations empowers teams to make informed decisions, scale resources as needed, and maintain a high level of application availability and responsiveness. Teams will be able to identify issues promptly and enable proactive optimization. Incorporating observability and responding quickly to your environment helps ensure operational efficiency, security, and compliance through continuous monitoring and informed decision-making.
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.