Designing a multi-account cloud chargeback model
WHAT IT TESTS: cost allocation architecture. OUTLINE: account-per-team or mandatory cost-allocation tags enforced by SCPs and tag policies, plus a pipeline over the cost and usage report grouped by tag/account. RED FLAG: relying on voluntary tagging.
WHAT IT TESTS: whether you can build enforceable, accurate cost attribution across many accounts. ANSWER OUTLINE: use organizational structure so each team maps to accounts or OUs, enforce mandatory cost-allocation tags through Service Control Policies and tag policies that deny resource creation without required tags, activate those tags for billing, and build a pipeline that ingests the Cost and Usage Report into a warehouse, joining account and tag dimensions to produce per-team reports including shared and untagged costs.
Read the original → interview
- #cloud
- #finops
- #chargeback
- #governance
- #tagging
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.