Skip to main content
AWS Config charges for every configuration item it records. Accounts that launch and terminate many EC2 Spot instances each day create a stream of items for every instance, network interface and volume. nOps finds accounts where the daily number of Config items rises and falls with the number of Spot instances, and estimates the saving from excluding those resource types from continuous recording.

Why it matters

In Spot-heavy accounts, such as Kubernetes or batch clusters, Config can cost more than expected because each short-lived instance is recorded several times.

How nOps finds it

nOps compares the daily number of Config items with the daily number of distinct Spot instances in each account over the last 30 days. An account is flagged when there are at least 21 days of data, the two move together (correlation of at least 0.5), and it ran at least 100 Spot instances a day on average in the last 7 days. nOps estimates the items each Spot instance adds from that relationship. The saving is that share of the Config item cost in the last 7 days, scaled to a month, at your billed price per item, and must be at least $50 a month.

Before you start

Know which Config rules and Security Hub controls apply to EC2 instances, network interfaces and volumes. Permission to change the configuration recorder (config:PutConfigurationRecorder).

How to implement

  1. Check which Config rules, conformance packs and Security Hub controls evaluate EC2 instances, network interfaces and volumes.
  2. In the AWS Config console, open Settings → Edit for the recorder.
  3. Either exclude the resource types EC2 Instance, EC2 NetworkInterface and EC2 Volume from recording, or set their recording frequency to daily instead of continuous.
  4. For many accounts, make the change in the organization’s recorder template (for example CloudFormation StackSets or Control Tower settings).
  5. Check the Config bill after a week.

Risks and considerations

  • Config rules and Security Hub controls on those types will see daily changes or none. Confirm your compliance needs allow it.
  • Short-lived Spot instances recorded daily may not appear in Config at all.
  • To roll back, set the resource types back to continuous recording.

FAQs

Config recording is set per account and region, so the change and the saving apply to the account.