Platform, cost & AI
Cloud cost control (FinOps)
Cloud cost has become part of the DevOps job description. Companies expect platform engineers to know where the money goes, to design for cost as well as reliability, and to cut waste without hurting production. In interviews it shows up as "our AWS bill doubled, what do you do?", "Spot or Savings Plans?" and "how do you split EKS costs between teams?". This topic covers how AWS charges, how to get visibility, how to optimise compute, Kubernetes, storage and data transfer, and how to make cost control stick.
After this topic you can
- Find where cloud money goes with tags, accounts and billing tools
- Cut compute, Kubernetes, storage and data-transfer costs safely
- Combine Savings Plans and Spot and make cost control part of normal work
Lessons
-
1Why cost is an engineering problem
- FinOps in one page
- Unit economics
- How AWS charges
-
2Visibility first
- Allocation: who spends what
- Tools
- Showback and chargeback
- Kubernetes cost allocation
-
3Optimising compute
- Rightsizing and modernising
- Paying less for what you use
- Kubernetes-specific savings
-
4Storage, data transfer and managed services
- Storage
- Data transfer
- Managed services and architecture
-
5Making it stick
- Guardrails and habits
-
6Interview questions and model answers
- "Our AWS bill doubled last month. What do you do?"
- "Spot, Savings Plans or Reserved Instances?"
- "How do you split EKS costs between teams?"
- "How do you reduce Kubernetes costs without hurting reliability?"
- "NAT gateway costs are high. Why, and what do you do?"
- "How do you get engineers to care about cost?"
- "What are the risks of buying Savings Plans?"