FinOps Engineering Fundamentals 📖 FinOps Framework
Overview This document covers FinOps engineering fundamentals including the FinOps framework, lifecycle phases, personas, and the engineer's role in implementing FinOps practices. Understanding the framework is essential for the FinOps Certified Engineer exam.
FinOps Framework Definition FinOps is a cloud financial management discipline and cultural practice that brings financial accountability to the variable spend model of cloud. It enables organizations to get maximum business value by helping engineering, finance, and business teams collaborate on data-driven spending decisions.
Core Principles Teams need to collaborate - Engineering, finance, and business work togetherEveryone takes ownership - Engineers own cloud cost as a metricA centralized team drives FinOps - Central team enables organizational adoptionReports should be accessible and timely - Real-time visibility into costsDecisions are driven by business value - Not just cost reductionTake advantage of the variable cost model - Cloud flexibility is a feature 📖 FinOps Principles
FinOps Lifecycle Phases Phase Focus Activities Inform Visibility and allocation Cost reporting, tagging, showback/chargeback Optimize Identify savings Right-sizing, reserved instances, waste elimination Operate Continuous improvement Governance, automation, cultural practices
📖 FinOps Phases
Maturity Model Level Characteristics Metrics Crawl Basic visibility, reactive optimization Cost allocation > 50% Walk Proactive optimization, automation starting Cost allocation > 80% Run Full automation, culture embedded Near 100% allocation, continuous optimization
Organizations may be at different maturity levels for different capabilities Not every capability needs to be at "Run" level Progress is iterative - crawl before you walk FinOps Personas Engineering Teams Responsibility: Build cost-efficient applications, respond to optimization recommendationsMetrics: Cost per transaction, cost per user, resource utilizationActions: Right-size resources, implement auto-scaling, use spot/preemptible instances Finance Teams Responsibility: Budgeting, forecasting, cost allocationMetrics: Budget variance, cost per business unit, ROIActions: Define budgets, create showback/chargeback models, forecast spend Business/Product Teams Responsibility: Define business value metrics, prioritize spendingMetrics: Revenue per cloud dollar, customer acquisition costActions: Approve spend, define business value of features FinOps Practitioner (Central Team) Responsibility: Enable FinOps practice, provide tools and processesMetrics: Organization-wide savings, adoption rate, coverageActions: Build dashboards, negotiate rate optimization, establish policies Responsibility: Champion FinOps culture, approve organizational changesMetrics: Total cloud spend trend, unit economicsActions: Set organizational goals, fund FinOps team, enforce accountability Engineer's Role in FinOps Cost Awareness Understand cloud pricing models for services you use Monitor cost impact of architecture decisions Include cost as a non-functional requirement in design Review cost impact before deploying new resources Tagging and Allocation # Standard tagging strategy
Tag Key | Purpose | Example Values
-----------------|------------------------|------------------
team | Cost allocation | platform, data, ml
environment | Environment tracking | dev, staging, prod
project | Project attribution | search-v2, payments
cost-center | Finance mapping | CC-1001, CC-2050
owner | Accountability | alice@company.com
service | Service identification | api-gateway, worker
Cost-Efficient Architecture Right-size resources - Match instance types to actual workload needsAuto-scale - Scale in/out based on demand, not peak provisioningUse managed services - Serverless/managed services reduce idle costStorage tiering - Move infrequent data to cheaper storage classesRegional selection - Consider price differences between regionsSpot/Preemptible - Use for fault-tolerant, interruptible workloads Cloud Pricing Models Compute Pricing Model Commitment Discount Flexibility On-Demand None 0% Full flexibility Reserved/Savings Plans 1-3 years 30-72% Limited flexibility Spot/Preemptible None 60-90% Can be interrupted
Storage Pricing Tier Access Pattern Cost Example Hot/Standard Frequent access Highest S3 Standard, GCS Standard Warm/Infrequent Monthly access Medium S3 IA, GCS Nearline Cold/Archive Yearly access Lowest S3 Glacier, GCS Coldline
Data Transfer Pricing Ingress (into cloud): Usually free Egress (out of cloud): Charged per GB Cross-region transfer: Charged per GB Same-region transfer: Often free or reduced This is often an overlooked cost driver FinOps KPIs Cost Efficiency Metrics Metric Formula Target Cost per unit Cloud cost / business metric Decreasing Resource utilization Used capacity / provisioned capacity 60-80% Waste percentage Idle/unused cost / total cost < 5% Coverage rate Committed resources / total resources 60-80% Tag compliance Tagged resources / total resources > 90%
Business Value Metrics Revenue per cloud dollar Cost per customer Cost per transaction Infrastructure cost as percentage of revenue Feature development cost per release Cloud Provider Native Provider Cost Tool Recommendations Budgets AWS Cost Explorer Cost Optimization Hub AWS Budgets Azure Cost Management Azure Advisor Azure Budgets GCP Cloud Billing Recommender GCP Budgets
Apptio Cloudability Spot by NetApp (Spot.io) Kubecost (Kubernetes) Infracost (Terraform) Vantage CloudHealth by VMware OpenCost (Kubernetes cost monitoring) FOCUS (FinOps Open Cost and Usage Specification) Cloud Custodian (policy-based management)