AWS Config cost explained: you're billed per change, not per resource

Quick answer

AWS Config bills ~$0.003 per configuration item recorded (a snapshot each time a resource changes) plus ~$0.001-0.003 per rule evaluation. The bill is driven by churn × scope: recording every resource type in every region means high-change resources stream items at $0.003 each. Cut it by recording only the resource types and regions you actually need for compliance.

AWS Config is easy to turn on org-wide and forget — and that's exactly how it becomes a line item nobody owns. The cost isn't per resource; it's per change, so a fleet of frequently-changing resources recorded everywhere generates a quiet, steady stream of billable configuration items.

The cost model

Configuration items: ~$0.003 each. One is recorded whenever a tracked resource is created, modified, or deleted. The dominant cost.
Rule evaluations: ~$0.001-0.003 each (tiered by volume), for Config rules and conformance packs.

Churn × scope is the bill

Two things multiply: how many resource types you record, and how often those resources change. Recording all types in all regions across an organization captures high-churn resources — Auto Scaling activity, network interfaces, ephemeral compute — each emitting configuration items on every change. At $0.003 an item across a large estate, that's a meaningful monthly cost for history that's rarely queried.

How to keep it down

Scope the recorder. Record the resource types your compliance and audit actually need — IAM, security groups, S3, key infrastructure — not every type by default.
Exclude high-churn noise. Resource types that change constantly and add little audit value are pure configuration-item volume; exclude them.
Limit regions. Record in the regions you operate in, not all of them.
Prune unused rules. Rule evaluations you never act on still bill — keep the rule set to what you enforce.

It's the same lesson as CloudTrail data events and CloudWatch metric cardinality: governance and observability services bill by volume, so scope is the whole game.

FAQ

How is AWS Config priced?

Mainly per configuration item recorded — about $0.003 per item — where an item is a snapshot of a resource's state whenever it changes. On top of that, Config rule evaluations cost roughly $0.001-0.003 each depending on volume, and conformance packs bill per evaluation too. The configuration items are usually the dominant cost.

Why is my AWS Config bill higher than expected?

Usually recording everything, everywhere. If Config records all resource types in all regions and accounts, high-churn resources (Auto Scaling groups, network interfaces, anything that changes frequently) generate a stream of configuration items at $0.003 each. Multiplied across an organization, that adds up fast for data many teams never query.

What is a configuration item?

A point-in-time record of a resource's configuration, created whenever the resource is created, changed, or deleted. A resource that changes often produces many configuration items, and you're billed per item — so churn, not just resource count, drives the cost.

How do I reduce AWS Config costs?

Scope recording to the resource types you actually need for compliance rather than recording everything, exclude high-churn resource types that generate noise, limit recording to relevant regions, and prune Config rules you don't act on. Recording selectively is the biggest lever.

Do I need to record every resource type?

Rarely. Most compliance and audit needs are satisfied by recording a defined set of resource types (IAM, security groups, S3, etc.). Recording every type in every region 'to be thorough' generates configuration items — and cost — for resources no rule or audit ever examines.

How does C3X relate to AWS Config cost?

Config cost is usage-driven by configuration-item volume, so C3X models it from expected item and rule-evaluation counts in c3x-usage.yml and prices the related resources, helping you attribute Config spend to the recording scope that generates it.

What to do next

Config cost rides on recording scope and resource churn — both worth deciding deliberately. C3X models Config item and rule-evaluation volume as usage and prices the related resources, so you can attribute the spend to the recording scope behind it. The quickstart runs it in minutes.