Opscraft
Cloud cost control (FinOps) · Lesson 5 of 6 · 3 min read

Making it stick

Guardrails and habits

  • Cost in code review: tools like Infracost comment on Terraform pull requests with the monthly cost change, so expensive changes are visible before they're applied.
  • Policies: SCPs that block unused regions and very large or GPU instance types except in approved accounts; tag policies; Config rules for untagged or unencrypted resources.
  • Budgets per team with alerts to the team's channel, and anomaly alerts routed the same way.
  • A regular cost review (weekly or fortnightly) with engineering: top changes, anomalies, recommendations, owners and due dates.
  • KPIs that matter: unit cost, commitment coverage and utilisation, percentage of spend allocated to an owner, idle and waste percentages.
  • Celebrate savings like performance wins, and don't let cost-cutting remove redundancy that protects availability: savings that cause an outage aren't savings.
Enlarge diagrampull requestadd 3 ×r6g.2xlargeInfracost+$1,240 / monthreviewneeded? smaller?Spot?mergewith eyes open
Figure 1. Make cost visible before it is spent: a cost estimate on every Terraform pull request.
Swipe sideways to see all of it, or tap to open it full screen.