AWS Cost Reduction - Experiences and Strategies
summary
Catalyst documents concrete practices: they cut AWS spend by 30–40% reduction through audits, tagging and account separation, pragmatic use of reserved instances and spot instances, and moving large shared disks to object storage rather than EBS. They run workloads on ECS (now considering Kubernetes), automate monitoring to kill runaway Lambda or worker growth, benchmark instance-size vs cost with load tests, and warn that lift‑and‑shift VMs often increase costs rather than save them.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:33About Catalyst IT
- 1:57About this talk
- 2:56Catalyst and AWS
- 5:33Before AWS
- 7:47Why manage cloud spend
- 10:27Vendor lockin
- 13:05Knowledge is power
- 14:16Cloud isnt always cheaper
- 17:05Responsibility
- 18:07Turn stuff off
- 18:38Ask questions
- 19:32Care or not pits
- 21:36Reserved Instances
- 23:32Block Storage
- 25:04Object Storage
- 27:24Backup and Retention
- 29:18Tags
- 30:54Relational Databases
- 32:01Cost Reduction Tools
- 34:12Make Targets
- 35:17Docker
- 37:54What static should I choose
- 40:28Always green approach
- 42:49Serverless
- 45:16Questions
related talks
55mOptimizing Costs on AWS Cloud
56mSaving on AWS? If not, what are you waiting for?
43mCost optimization: Actionable steps for immediate results
27mMastering AWS Cost Optimisation
18mThe nonstop way to find AWS-recommended savings opportunities
41mFinOps and Cloud Cost Optimization
17mBoosting Cost Efficiency by Cost Aware Architecture
32mCreate a cloud-ready environment