Explanation
Why the waste happens and who it affects.
While this may be justified for production workloads where detailed auditability is critical, it is rarely necessary in non-production environments. Frequent changes in development or testing environments - such as redeploying Lambda functions, ECS tasks, or EC2 instances - generate large volumes of CIRs. This results in disproportionately high costs with minimal benefit to governance or compliance. Switching frequently changing resource types in non-production environments to daily recording reduces CIR volume significantly while maintaining sufficient visibility for tracking changes.
Billing model
The pricing dimensions that drive this cost.
AWS Config charges per Configuration Item Recorded (CIR). Continuous mode generates a CIR for every resource change, while daily mode generates a maximum of one CIR per resource per day, and only if the resource changed. Daily CIRs are priced higher than continuous CIRs ($0.012 vs $0.003 per CIR in the US East (N. Virginia) pricing example), so daily recording lowers cost only for resources that change more than about four times per day. In non-production environments with frequent deployments or updates, continuous mode creates unnecessary cost without meaningful compliance value.
How to detect
4 checks to find it in your estate.
- Review whether AWS Config is set to continuous recording in non-production accounts or environments
- Evaluate change frequency in development, QA, and staging systems to estimate unnecessary CIR volume
- Confirm whether governance or compliance requirements justify continuous recording in these environments
- Assess consistency of recording settings across production vs. non-production accounts
How to fix
3 ways to remove the waste.
- Update AWS Config settings in non-production accounts to daily recording frequency instead of continuous for resource types that change frequently, using recording frequency overrides to set this per resource type
- Apply environment-specific configuration baselines to enforce lower granularity tracking outside of production
- Validate that compliance and auditing needs remain satisfied after reducing recording frequency
Documentation
Vendor references for pricing and configuration.