Price the switch before turning it on.
Two expense rules caught two different billing clocks before they became recurring infrastructure: an hourly endpoint and a multi-account, multi-Region control plan.
Declare cost in the same change that creates it.
Update the living expense report in the same pull request.
No file traffic did not mean no endpoint charge.
The AWS Transfer Family pricing example reviewed in July 2026 used $0.30 per endpoint-protocol hour, or $216 over 30 days, before transfer charges. This is dated US East example math—not a current universal quote.
We preserved the Terraform design behind an explicit disabled-by-default switch and recorded the estimate beside the decision.
One policy could expand across accounts and linked Regions.
Security Hub central configuration applies policies in the home and linked Regions. Many control findings depend on AWS Config recording, whose charges depend on recorded items and evaluations. The failed rollout became a pause for an explicit coverage and cost model.
Historical inputs
Then-current accounts × then-linked Regions.
Current estimate
Actual scope × resource churn × recording mode × live pricing.
An RDS stop needs an owner for day seven.
AWS documents that a stopped RDS DB instance automatically restarts after seven days. Stopping an idle development database can reduce spend, but it is not a permanent control without scheduling or review.
Every paid change names its meter and exit.
Unit
Hour, endpoint, Region, account, item, evaluation, request, or gigabyte.
Multiplier
How architecture scope amplifies the unit.
Shutdown path
Disable without erasing the design.
Owner
Who validates the estimate and next invoice.
Before approving a paid cloud change.
- What starts the meter?
- What multiplies it?
- Does idle still bill?
- What safely turns it off?
- Who verifies actual spend?
Use live pricing for live decisions.
AWS Transfer Family pricing · AWS Config pricing · Security Hub central configuration · RDS stop/start behavior
Educational, dated observations only. Costs vary by time, Region, usage, scope, taxes, and architecture. Monthly spend does not establish HIPAA compliance.
Price the switch before turning it on.
A narrated visual edition about hourly clocks, regional multipliers, and the pull-request cost contract.