[text]
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]
Architecture Diagram
[text]
Step 1
Deploy and configure log analysis tools and filters to identify key events within your AWS Organization using sources from an AWS CloudTrail organization trail and events in Amazon EventBridge.
Step 2
Centralize log visibility across your AWS Organization using Amazon CloudWatch cross-account observability.
Step 3
Build CloudWatch metrics to filter and alert based on key performance indicators and operational events.
Step 4
Build and share dashboards and visualizations using CloudWatch, and set up CloudWatch alarms that notify you when resources reach a pre-defined threshold.
Step 5
Centralize persistent long-term log storage for CloudWatch logs, CloudTrail logs, and AWS Config logs to manage lifecycle and cost optimization.
Step 6
Implement automated log archival by exporting CloudWatch logs to a centralized Amazon Simple Storage Service (Amazon S3) bucket.
Step 7
Centralize operational and security events across your AWS Organization by using EventBridge and EventBridge rules.
Step 8
Define EventBridge rules to send notifications to actionable team members using Amazon Simple Notification Service (Amazon SNS) topics.
Step 1
Deploy and configure log analysis tools and filters to identify key events within your AWS Organization using sources from an AWS CloudTrail organization trail and events in Amazon EventBridge.
Step 2
Centralize log visibility across your AWS Organization using Amazon CloudWatch cross-account observability.
Step 3
Build CloudWatch metrics to filter and alert based on key performance indicators and operational events.
Step 4
Build and share dashboards and visualizations using CloudWatch, and set up CloudWatch alarms that notify you when resources reach a pre-defined threshold.
Step 5
Centralize persistent long-term log storage for CloudWatch logs, CloudTrail logs, and AWS Config logs to manage lifecycle and cost optimization.
Step 6
Implement automated log archival by exporting CloudWatch logs to a centralized Amazon Simple Storage Service (Amazon S3) bucket.
Step 7
Centralize operational and security events across your AWS Organization by using EventBridge and EventBridge rules.
Step 8
Define EventBridge rules to send notifications to actionable team members using Amazon Simple Notification Service (Amazon SNS) topics.
Additional Considerations
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.
Related Content
- Stakeholders: Central IT (primary), Security, Operations, Finance
- Supporting Capabilities: Governance, Workload Isolation, Log Storage, Identity Management and Access Control
- For additional information on this capability, read the whitepaper.
Disclaimer
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.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.