Skip to main content

Blog category

Cost Optimization & FinOps

Articles in this topic
71
4 min

Post-Migration Optimization and the FinOps Handoff (2026): The First 30 Days After Cutover Decide Your Run-Rate

A lift-and-shift migration copies on-prem specs sized for peak plus headroom, then the migration partner rolls off and nobody owns the bill. The waste is predictable: 30 to 60% of cost untagged, over-provisioned EC2/RDS, idle NAT Gateways and orphaned EBS, and commitments bought on top of all of it. This is the explicit migration-to-FinOps handoff: owner first, visibility second, right-size before you commit. It comes with a 30-day checklist and an optimization-backlog CSV.

Kevin W.
6 min

AWS Tagging, Chargeback, and FinOps Ownership (2026): Tag Policy vs SCP, the Untaggable 21%, and Splitting Shared Cost Without a Spreadsheet War

Tag policies report; only an SCP prevents untagged spend. And ~21% of a typical bill (egress, inter-AZ transfer, Enterprise Support, shared platform services) carries no tag any tool can read. The post covers the two-layer enforcement model, the Cost Categories split-charge rules that replace the monthly allocation spreadsheet, and why you show back before you charge back.

Kevin W.
8 min

Reserved Instances vs Savings Plans on AWS (2026): The Three-Way Choice, the 22-Month Break-Even, and When to Skip Commitment Entirely

Most "RI vs Savings Plan" content treats them as peers. In mid-2026 they are not. A 3-year All-Upfront Compute Savings Plan saves a composite ~$60k/mo SaaS roughly $864k over 3 years vs a 1-year No-Upfront plan, but breaks even at ~22 months and locks instance-family flexibility. Buy the wrong commitment and a Graviton migration strands the discount. This post gives the decision tree we use.

Kevin W.