The irony of cloud cost-cutting: when saving money leads to losing money
summary
TIER Mobility cuts cloud spend by 60% in less than two years but reveals costly tradeoffs: AWS EC2 tweaks and Spot help only when workloads tolerate disruption, Savings Plans and Reserved Instances lock capital and fail under M&A, and resellers like Hikl buy flexibility at a fee. Buying a Kubernetes cost product spikes the cluster by 10–15% to run analytics; visibility shows hundreds of microservices with 95% costing under $100 each and only ~$20–30 of optimizable savings per service, while migrating CI (CircleCI → GitLab) and managed services proves far slower and pricier than expected.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 1:05Cloud cost savings pitfalls
- 2:12EC2 cost reduction strategies
- 5:04Reserved instances and savings plans
- 9:18Business alignment for commitments
- 10:23Network cost challenges
- 13:43Kubernetes cost transparency
- 19:44Vendor lock-in risks
- 23:39Summary and takeaways
- 24:24Q&A session
related talks
14mCut Costs, Not Performance: Implement Kubernetes Cost Optimization Strategies
23mFinOps and Cloud Cost Optimization
43mBuilding Monetary Confidence in the Cloud
49mAWS Cost Reduction - Experiences and Strategies
45mCloud Computing: Cloud in a cost-effective way
05mFive Minute Cost-Optimisation
43mMigration to the Cloud, DevOps Perspective
47mCost optimization