Cost Control
Part of Cloud cost management
Reading a cloud bill by service and workload
Reconcile the billed total, inspect service charges and billing units, and keep shared or unassigned workload costs visible.
Read a cloud bill in two passes. First confirm the billed total for the correct period and billing account. Then trace material service charges through their billing units and resource detail to the workloads that used them. A service name alone does not identify the team or application that benefited.
Confirm the total and its basis
Use a closed billing period when explaining an invoice. Record the billing entity, currency and included accounts, subscriptions or projects. Show usage, commitment purchases, recurring fees, credits, adjustments and tax separately. An open-period dashboard is an estimate; a final invoice can include later-reported or invoice-level items.
Keep date and cost bases consistent when comparing periods. AWS billing and analytical views can differ in grouping, credits, tax, timing and rounding. If an internal report amortises eligible commitments, use an actual-charge view to bridge it to the invoice.
Follow material service charges
Sort services by amount or change, then inspect the relevant meter or SKU, billable quantity, unit and region where available. More units, a different rate, an upfront purchase or a changed credit can each raise the amount. Record the specific line requiring an explanation.
| Provider | Starting view | Limit to check |
|---|---|---|
| AWS | Bills for closed-period charges; Cost Explorer for service, linked account, usage type and activated cost-tag filters | Cost Explorer and invoice presentations need reconciliation. A cost tag must be activated before it appears in those reporting views. |
| Azure | Cost Analysis grouped by service, with filters for subscription, resource group, meter or tag | Cost Analysis groups by one attribute at a time; some services can lack a usable resource or tag. |
| Google Cloud | Billing Reports grouped by service, project or SKU | Permissions affect the visible scope. Standard billing export does not provide resource-level cost detail; detailed export adds it. |
These views explain a bill from the chosen provider; they do not compare provider prices.
Cloud Provider Billing Views and Limitations
- AWSBills for closed-period charges; Cost Explorer for service, linked account, usage type and activated cost-tag filters. Cost tags must be activated before appearing in reports.
- AzureCost Analysis grouped by service with filters for subscription, resource group, meter or tag. Groups by one attribute at a time; some services lack usable resource or tag.
- Google CloudBilling Reports grouped by service, project or SKU. Permissions affect visible scope. Standard export lacks resource-level detail; detailed export adds it.
Build workload totals
Map each material charge to its account, project or subscription, then to a workload using a reliable label, resource record or other billing detail. Include associated storage, transfer, shared platforms and non-production environments where they belong.
Keep costs directly assigned, shared under an agreed rule, or unassigned pending investigation. A shared database needs an explicit split or central pool. Preserve the service, billing unit, period and possible owner for an unresolved charge; do not silently distribute it.
Reconcile the bridge
Start with the invoice total. Identify purchases, credits, adjustments and tax separately, then derive the service-usage subtotal on a stated basis. Check that assigned workload amounts, shared allocations and unassigned usage sum to that subtotal.
Record differences due to timing, rounding or missing detail. If a label was applied partway through the period, leave earlier usage unlabelled unless other evidence supports its assignment.
