POST No AWS Bills: Cloud Cost Optimization without APIs
summary
Claims that off‑the‑shelf cloud cost tools fail to capture real business insight, backed by hands‑on experiments: a netcat + dd experiment exposes data‑transfer oddities (AZ vs region costs, cheap VA‑Ohio path), load balancers use opaque LCU pricing opacity that is nondeterministic, and NAT gateways charge about $0.045/GB NAT gateway pushing surprise data‑transfer bills. Also note storage math: S3 ~2.3¢/GB versus EBS ~23¢/GB, total addressable market for such tools ~$1B on a $35B AWS revenue, and isolated engineering fixes have cut tens of millions from bills.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:24It's the fault of Venture Capitalists!
- 4:34A brief digression
- 10:59Allocation and
- 11:31The AWS bill has tax consequences
- 12:45Visibility and Predictability freaking Matter!
- 15:11What does Engineering care about?
- 26:06Data Transfer
- 28:07Does anyone know how much an Application Load Balancer costs?
- 31:06Managed NAT Gateways
- 32:11Data Lifecycle Policies
related talks
55mOptimizing Costs on AWS Cloud
30mAnd the CFO Wept: AWS Cost Control
40mWhat a Cloud Bill Can Reveal
27mMastering AWS Cost Optimisation
49mAWS Cost Reduction - Experiences and Strategies
18mThe nonstop way to find AWS-recommended savings opportunities
31mThe AWS Billing Machine and Optimizing Cloud Costs
45mCloud Computing: Cloud in a cost-effective way