Cloud financial accountability for engineering teams
Day 1
FinOps Principles, Cost Visibility & Optimization
- FinOps framework: inform, optimize, operate — the three phases
- Cost allocation: tagging strategy, cost centers, showback vs chargeback
- AWS Cost Explorer, Azure Cost Management, GCP Cost Management: reading and comparing
- Reserved Instances vs Savings Plans vs Committed Use Discounts: trade-off analysis
- Spot/Preemptible instances: savings, interruption handling, use cases
- Rightsizing: identifying over-provisioned EC2, VMs, and databases
- S3/Blob storage optimization: lifecycle policies, intelligent tiering, storage class analysis
- Data transfer costs: the hidden bill — egress fees and how to minimize them
- Kubernetes cost visibility: Kubecost, OpenCost — pod-level cost attribution
- Unit economics: cost per request, cost per user, cost per transaction
- Waste identification: idle resources, unattached volumes, forgotten load balancers
- Automation: scheduled scaling, auto-stop dev environments, spot instance automation
What your team walks away with
Engineering teams who treat cloud cost as an engineering concern — measured, attributed, and optimized continuously rather than discovered at month-end.
- Set up a tagging strategy that enables cost attribution by team, service, and environment
- Identify rightsizing opportunities and quantify the savings before acting
- Choose between reserved capacity and savings plans based on workload stability
- Implement automated cost controls: budgets, alerts, and idle resource cleanup
Book the FinOps training
Especially valuable for teams who have been running in the cloud for 6+ months and are seeing the bill grow unexpectedly.
Get in touch