# AWS Config Recorder

> AWS Config's recorder bills per configuration item recorded each time a tracked resource changes, plus per-evaluation charges from the rules layered on top. Recording all resource types in a busy account produces a steady charge. ZopNight tracks Config cost from Cost Explorer or CUR 2.0 and recommends narrowing the recording scope.

Source: https://zop.dev/integrations/aws/config-recorder
Updated: 2026-08-19

---

The AWS Config recorder tracks resource configuration changes, billed per configuration item recorded plus rule evaluations. Recording all resource types in busy accounts produces a steady, often unexamined monthly charge.

## Billed by change, scoped by default to everything

Each time a recorded resource changes, Config writes a configuration item and bills for it. The recorder's scope decides the volume: the default and most common setup records all supported resource types, so the charge tracks how much the account churns (autoscaling events, deployment rollouts, tag edits, ephemeral ENIs) rather than how much anyone consumes the history. Continuous recording of high-churn types can be swapped for daily recording per type, which caps the per-resource cost at one item per day, a distinction most accounts never revisit after setup.

## ZopNight's angle on Config spend

A dedicated provider tracks the recorder configuration, with Config cost drawn from Cost Explorer or CUR 2.0. Recording-scope recommendations are the output: identifying the resource types generating most of the configuration items, flagging high-churn types (spot fleets, ENIs, autoscaling groups) where daily recording would preserve auditability at a fraction of the item volume, and surfacing accounts where recording runs at full scope though nothing reads the results: no rule, no aggregator, no auditor.

## The churn amplifiers

Autoscaling is the classic: every scale-out and scale-in writes configuration items for instances, ENIs, and volumes that live for an hour. Blue-green deployment tooling doubles item volume during every release. Sandbox accounts inherit the organization's full-scope recorder baseline and pay compliance-grade recording rates for throwaway experimentation. In each case the recording is technically correct and economically pointless.

## Where the recorder's settings live

The Config console's Settings page shows the recorder's scope, all types versus a list, and the recording frequency per type. Pairing that view with the service's own metrics on configuration items recorded per type identifies exactly which types drive the bill, and whether the audit trail anyone actually uses would survive a narrower scope untouched.