IaC Resource Count Calculator

Work out iac resource count instantly with clear inputs, formula shown and shareable results.

About IaC Resource Count Calculator

Resource count multiplies out across environments and services, so a modest estate reaches thousands of managed objects. Plan time grows with state size because every resource is refreshed against the provider, which is why splitting into state files of roughly 100 to 200 resources keeps plans fast and limits the blast radius of a bad apply.

Formula

Resource scale

total = environments x services x resources per service + shared; state files = ceil(total / 200)

Worked example

With the default values below, IaC Resource Count Calculator returns Total managed resources of 1,860. Change any input above and every figure here is recalculated in your browser.

Inputs used

Environmentsminimum 1: 4
Services per environmentminimum 1: 35
Resources per serviceminimum 1: 12
Shared platform resourcesminimum 0: 180

Results

Total managed resources: 1,860
State files to split into: 10
Resources per environment: 420
Estimated plan time if kept in one state: 419 s

Step by step

1Values used
2Resource scale
3Total managed resources= 1,860
4State files to split into= 10
5Resources per environment= 420
6Estimated plan time if kept in one state= 419 s

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to whole numbers, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How should state be split?

By blast radius and change frequency: per environment, then per bounded domain such as networking, data stores and application services.

Why is plan time a problem?

It is paid on every change. A twenty-minute plan discourages small changes, which pushes teams toward large risky applies — the opposite of what you want.