The Evolution of FinOps Culture at Avis Budget Group
summary
Avis Budget Group hires a dedicated FinOps analyst, runs the AWS Cloud Financial Management capability assessment, and builds a tagging-first program that enforces Terraform-enforced tags so no resource deploys without a project name tag and business unit tag. Teams backfill legacy resources, add tag-based AWS Budgets, and adopt a KudoS dashboard to surface issues (found S3 intelligent‑tiering off). EKS namespaces map value streams for per‑team visibility, monthly business reviews deliver actionable right‑sizing and Savings Plan opportunities, and optimization becomes an ongoing cycle.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 0:45Company overview and FinOps basics
- 2:12What is FinOps and its three phases
- 5:27AWS Cloud Financial Management framework
- 6:50Avis Budget Group’s FinOps journey
- 8:16AWS FinOps assessment process
- 12:36Adopting FinOps culture at ABG
- 14:25Differentiating optimization needs
- 18:38Key takeaways after FinOps assessment
- 20:48Tagging strategy and dashboards
- 22:55Enforcing tagging policies
- 26:52Policy enforcement methods
- 28:19Advice for FinOps newcomers
- 30:05Shared services and Kubernetes strategy
- 32:32Tracking savings and next steps
related talks
38mFinOps and Tag Strategy on AWS
12mFinOps on AWS: Accelerated outcomes to maximize ROI
25mBuilding a FinOps practice to realise the true value of cloud
19mFinOps for business results
27mWith FinOps Through the Cloud Cost Jungle
36mFinOps & Observability: technical implementation
31mArchitecting an Optimal FinOps Platform
31mGetting the Most out of Every Dollar Spent in Cloud