Three Technical Account Managers (TAMs) from DoiT join us to share three stories around customers overspend + dealing with cloud commitment drawdowns, and the lessons you can implement into your own cloud cost management strategy, regardless of whether you use the services mentioned.
Additional Resources
- Topology Aware Hints for EKS: aws.amazon.com/blogs/containe...
- 7 not-so-obvious red flags in your cloud bill: • The not-so-obvious red...
About the guests
Ieva Jonaityte ( / ieva-jonaityte-4135411a3 , Ian Hart ( / ian-hart , and Eric Ethridge ( / ericethridge ) are Technical Account Managers at DoiT, where he provides technical consulting and support to high-value, technically demanding customers. In their roles they plan architectures, review costs, identify future growth opportunities, and develop training pathways for existing and potential customers.
Key Moments
00:00 Introduction
00:56 What do TAMs do?
02:22 EKS and splitting Spot instances across AZs
03:42 Topology Aware Hints in EKS
04:46 Takeaway = Regularly review your architecture
07:43 Usage creeping up? That's your signal to review
08:35 What to do when you're falling behind on an EDP
09:50 Breakeven point with Savings Plans/RIs
11:58 Staggering upfront SP purchases
13:55 Using Flexsave coverage as a benchmark for 3-year Savings Plans and RIs
15:08 View your commitments analytically, not emotionally
17:02 Using Marketplace purchases to burn down commits
20:31 Unnecessarily using Persistent Disks
23:27 Making technology decisions without questioning the "why"