Optimize AWS event and log collection using common design patterns
Integration & Automation Blog
This article discusses approaches and patterns for optimizing the collection and consumption of event and log data across multiple AWS accounts in an organization.
Specifically, the article covers:
- Approach 1: Collecting logs in a centralized Amazon CloudWatch monitoring account
- Approach 2: Collecting logs in an Amazon S3 bucket in a centralized log archive account
- Pattern A: Sending Amazon S3 event notifications through Amazon SQS
- Pattern B: Sending Amazon S3 event notifications through Amazon SNS
- Pattern C: Fanning out Amazon S3 event notifications using a combination of Amazon SNS and Amazon SQS
- Pattern D: Performing centralized logging with Amazon OpenSearch Service
- Conclusion and recommendations for implementing the patterns using CloudFormation templates
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jul 15
2024
2024
Patterns for consuming custom log sources in Amazon Security Lake
Sep 25
2025
2025
Simplifying Log Management using Amazon CloudWatch Logs Centralization
Dec 20
2024
2024
Adapting to change with data patterns on AWS: The “aggregate” cloud data pattern
Dec 19
2025
2025
AWS IoT now offers event-based logging to help optimize observability costs
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.