# Amazon CloudWatch Logs Published articles for Amazon CloudWatch Logs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Customize Amazon API Gateway destinations for execution logs DevFeed: [Customize Amazon API Gateway destinations for execution logs]() Original publisher: [Read original article]() Author: Giedrius Praspaliauskas Published: 2026-09-09T22:35:42Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [Amazon CloudWatch Logs](), [log management](), [Amazon S3](), [SIEM, Security, Observability]() Tags: [amazon-api-gateway](), [amazon-cloudwatch-logs](), [amazon-s3](), [announcements](), [intermediate-200](), [logs](), [observability](), [rest-api]() ### AI overview This tutorial explains how to route Amazon API Gateway REST API execution logs to CloudWatch Logs, Amazon S3, or Amazon Data Firehose. It contrasts execution logs with access logs and describes their use for diagnosing authorization, validation, integration, mapping, and error-handling behavior. ### Source excerpt Amazon API Gateway execution logs help you trace request processing step by step through your REST API stages. They capture authorization results, integration latency, mapping template output, and error details that are otherwise invisible at the API surface. When a production request fails in a way the access log cannot explain, the execution log is [...] ## From noise to signal: Monitoring Amazon DocumentDB like a pro DevFeed: [From noise to signal: Monitoring Amazon DocumentDB like a pro]() Original publisher: [Read original article]() Author: Deepak Deepesh Published: 2026-09-09T15:23:20Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon DocumentDB](), [site-reliability-engineering](), [Amazon CloudWatch Logs](), [Database]() Tags: [amazon](), [amazon-cloudwatch](), [amazon-cloudwatch-logs](), [amazon-documentdb](), [best-practices](), [database](), [devops](), [expert-400](), [health](), [how-to](), [logs](), [metrics](), [monitoring](), [on-call](), [operations](), [performance](), [production]() ### AI overview A tutorial on monitoring production Amazon DocumentDB clusters with tiered alerts, CloudWatch metrics, Performance Insights, profiler logs, slow-query diagnosis, and garbage-collection health checks. ### Source excerpt Learn how to build a tiered alerting strategy for Amazon DocumentDB by organizing CloudWatch metrics into Critical, Warning, and Advisory tiers, diagnosing slow queries through three complementary lenses, and monitoring garbage collection health before it becomes a cluster-wide incident. ## Detecting multi-stage attacks on AWS: A guide to cross-service signal correlation DevFeed: [Detecting multi-stage attacks on AWS: A guide to cross-service signal correlation]() Original publisher: [Read original article]() Author: Nisha Kashyap Published: 2026-08-26T17:39:19Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services (AWS)](), [Security](), [Detection engineering](), [Amazon CloudWatch Logs](), [AWS CloudTrail](), [VPC Flow Logs](), [Amazon S3](), [data]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-cloudwatch-logs](), [amazon-guardduty](), [amazon-route-53](), [amazon-web-services-aws](), [analysis](), [aws-cloudtrail](), [aws-security-hub](), [best-practices](), [cybersecurity](), [guide](), [incident-response](), [logs](), [s3](), [security](), [security-blog](), [security-identity-compliance](), [shared-responsibility-model](), [technical-how-to](), [threat-detection](), [vpc-flow-logs]() ### AI overview This article explains how security engineers can detect multi-stage attacks on AWS by correlating signals across services with business context. It presents examples using CloudWatch Logs Insights and discusses expanding the correlations into an automated pipeline. ### Source excerpt A single alert from one security service tells you something happened. Read that signal alongside activity from other services and your own business context, and you will know whether what happened is part of a multi-stage attack. Consider a short sequence. An identity calls GetCallerIdentity from a source address it hasn't previously used. Within minutes, [...] ## AWS Network Firewall now supports rule hit count DevFeed: [AWS Network Firewall now supports rule hit count]() Original publisher: [Read original article]() Author: Preetkumar Shah Published: 2026-08-20T18:40:20Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Firewall](), [Amazon Web Services](), [Amazon CloudWatch Logs](), [Network](), [Security](), [Amazon S3](), [log management](), [Incident response]() Tags: [amazon-cloudwatch](), [amazon-cloudwatch-logs](), [amazon-s3](), [announcements](), [aws](), [aws-network-firewall](), [compliance](), [firewall](), [incident](), [incident-response](), [intermediate-200](), [logs](), [network](), [s3](), [security](), [security-blog](), [security-identity-compliance](), [storage]() ### AI overview AWS Network Firewall now provides rule hit counts for stateful rules, using alert-log data to show how often rules match network traffic. The feature helps teams identify unused rules, support incident response, and demonstrate security-control effectiveness for compliance. ### Source excerpt As firewall rule sets grow in complexity, security teams face a common challenge: manual log analysis is used to determine which rules are actively matching traffic and which are consuming capacity without being triggered. This lack of visibility creates operational and compliance gaps. Organizations with governance policies that require removal of dormant rules after a [...]