Explanation
Why the waste happens and who it affects.
In change-heavy accounts (ephemeral resources, CI/CD churn, autoscaling), continuous mode drives very high CIR volumes with limited additional operational value. Selecting daily recording for lower-risk resource types and/or non-production environments can maintain necessary visibility while reducing CIR volume and cost. Recorder settings are account/region scoped, so you can apply continuous in production where required and daily elsewhere.
Billing model
The pricing dimensions that drive this cost.
Configuration Item Recorded (CIR)-based pricing: charges accrue for each configuration item that AWS Config records. Continuous recording records a configuration item for every change, while daily recording (the only periodic option) records at most one configuration item per resource per 24-hour period, and only if the resource changed. A daily configuration item costs four times as much as a continuous one ($0.012 vs. $0.003 per the AWS Config pricing page), so daily recording lowers cost only for resources that change more than about four times a day.
Note: AWS Config also has other pricing dimensions (e.g., rule and conformance pack evaluations). This entry focuses specifically on the CIR component.
How to detect
5 checks to find it in your estate.
- Identify accounts where AWS Config spend is dominated by configuration items recorded relative to overall cloud spend and risk profile.
- Confirm whether continuous recording is enabled broadly by default versus selectively by resource type/environment.
- Determine which resource categories experience frequent state changes and contribute disproportionately to recorded items.
- Validate with Security/Compliance/SRE whether per-change visibility is truly required for those categories.
- Assess whether observed recording volume aligns with actual investigative or audit needs.
How to fix
4 ways to remove the waste.
- Shift suitable resource types and/or non-production environments from continuous to daily recording where real-time change tracking isn't required.
- Scope recording frequency by environment: continuous for production or high-risk resources; daily for development/test or low-risk resources.
- Document the rationale and ownership (e.g., security vs. platform) to ensure shared expectations on visibility vs. cost.
- Monitor post-change configuration-item volume and spend to confirm expected reductions and adjust coverage as needed.
Documentation
Vendor references for pricing and configuration.