CloudWatch Logs enriches events with resource tags
CloudWatch Logs now ingests resource tags, enabling filtered analysis without code changes.
Editorial summary and commentary based on the original from AWS What's New. Read the original
What's new
- CloudWatch Logs now enriches log events with AWS resource tags at ingestion.
- Tag enrichment is available in all commercial AWS Regions except Middle East (UAE), Middle East (Bahrain), and Israel (Tel Aviv).
- No additional cost is associated with this feature.
Why it matters
This feature removes the operational burden of manually correlating log data with resource metadata. Previously, engineers needed to instrument applications to include tags in log messages or build separate data pipelines to enrich logs post-ingestion. Now, CloudWatch can automatically append tags like environment, team, or cost-center to log events. This simplifies filtering and searching logs during incident response or cost allocation, directly impacting Mean Time To Resolution (MTTR) and financial analysis accuracy. The primary trade-off is the limited region availability, which may delay adoption for teams operating in the excluded regions.
How to use it
Enable resource tag enrichment via CloudWatch Settings or the AWS CLI/SDK. Existing AWS resource tags will be automatically applied to ingested log events.
Source (AWS What's New): Amazon CloudWatch Logs enriches log events with AWS resource tags