Reduce AWS logging cost by fixing missing retention and self-targeted access logging before quiet log storage turns into recurring waste.
At a glance
AWS logging cost optimization is mostly about fixing default behavior that nobody revisits. Log groups are created with infinite retention, access logs are enabled without a dedicated destination, and the result is storage growth that does not feel urgent until months of quiet spend have passed.
This category groups the current Cloud Waste Hunter detector pages for AWS logging drift. The goal is to help operators find logging configurations that keep creating or retaining data without a clear cost boundary.
Prioritize first
If you're looking for the fastest ways to reduce waste in this category:
These deliver the clearest quick wins before deeper optimization work.
2 detectors included
Detector coverage
These detector pages cover the concrete waste signals that make up this broader category.
CloudWatch log groups with no retention policy default to infinite retention, which lets stored logs accumulate indefinitely and turn routine operational logging into background storage cost.
Detector ID
aws-cw-logs-no-retention
S3 access logging loop cost starts when a bucket writes access logs back to itself instead of a dedicated logging bucket. The issue usually appears when access logging is enabled quickly and the destination bucket choice is never revisited.
Detector ID
aws-s3-logging-loop
AWS logging cost optimization is mostly about fixing default behavior that nobody revisits. Log groups are created with infinite retention, access logs are enabled without a dedicated destination, and the result is storage growth that does not feel urgent until months of quiet spend have passed.
This category groups the current Cloud Waste Hunter detector pages for AWS logging drift. The goal is to help operators find logging configurations that keep creating or retaining data without a clear cost boundary.
The current detector set focuses on two common AWS logging cost problems:
These detectors belong together because both issues start with reasonable operational intent, then drift into avoidable storage cost when no one closes the loop on logging design.
Logging cost usually grows when:
Those conditions create log data that is technically useful to collect but much harder to justify keeping forever.
Start with CloudWatch log retention cost when storage growth is coming from indefinite retention on operational logs. Use S3 access logging loop cost and cleanup when the risk is a bucket-level logging configuration that can generate noisy or confusing self-referential storage behavior.
If the same review uncovers abandoned uploads or old versions inside logging buckets, continue into the AWS Storage Cost Optimization guide for the adjacent storage-governance cleanup work.
Related category guides
These category pages cover nearby cost-optimization themes that often surface during the same review cycle.
Start with CloudWatch log groups that have no retention policy and S3 buckets that write access logs back to themselves. Both are high-signal configuration issues that are easy to miss in day-to-day operations.
Retention drift is a major cause, but configuration mistakes that create unnecessary log data also matter. Good logging cost hygiene needs both separation and explicit lifecycle decisions.
They are different services, but the operator motion is similar. You need to confirm why logs are being kept, where they are being delivered, and whether the growth pattern is intentional.
Early Access
Cloud Waste Hunter is being built to connect these related waste patterns into a single review flow with savings estimates and remediation guidance.
