Watch Your Wallet! Cloud Anti-Patterns that Make Your AWS Bill Skyrocket
summary
Enable billing access and turn on AWS Cost Anomaly Detection so unexpected spikes trigger alerts, then measure before/after with tags or lifecycle-aware prefixes. Replace gp2 with gp3 volumes and move compatible instances to Graviton m6g where tests show Graviton m6g 20–30% savings and Migrate gp2→gp3 for ~20% cut. Avoid fixed IPs that force extra load balancers or Global Accelerator, use VPC endpoints instead of NAT gateways, and consider Lightsail for predictable low‑cost VPS workloads.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:10214 services 1733 price components
- 4:45hours
- 5:14nope!
- 6:56enable billing & cost management for your DevOps team
- 12:02compute
- 12:45avoid fix ips whenever you can
- 13:16Using static IP addresses for Application Load Balancers
- 14:47Achieve up to 52% better price/performance with Amazon RDS using new Graviton2 instances
- 16:32go old style, run on Lightsail (really!)
- 18:18data transfer
- 20:39Multi AZ is always better? 3 zones better than 2?
- 21:48Multi region? If you really have to
- 22:27Multi cloud: check all components
- 24:28CDN (CloudFront) might be cheaper
- 27:42What is an AZ destruction? Should I care?
- 29:36how do you distribute your objects/delete data in a bucket?
- 32:12watch out for automatic and manual snapshots / backups
- 35:02Things change quickly
- 37:20why?
related talks
27mMastering AWS Cost Optimisation
20mAtomics Habits in cost optimizations in the cloud
40mAvoiding Pain When Operating in the Cloud
31mThe AWS Billing Machine and Optimizing Cloud Costs
32mCreate a cloud-ready environment
34mOptimizing Cloud Efficiency with Prompt Engineering
23mFinOps and Cloud Cost Optimization
33mHow we do cloud cost efficiency at Notion