Synopsis
Use Cost Explorer to find the edge of the question
Cost Explorer is a good place to see when spend moved and which service, account, region, or usage type deserves attention. Treat it as orientation. Some questions end there; others need line-item evidence.
Observation
Start with movement, not the biggest total
Choose the time window, granularity, and cost metric before reading the chart. Compare complete periods where possible. Then follow the material changes from service into linked account, region, and usage type.
Procedure
A first pass you can repeat tomorrow
1. metric: unblended or amortized, chosen deliberately 2. granularity: daily for timing, monthly for trend 3. group: service → account → region → usage type 4. record: filters, dates, currency, observed delta 5. escalate: CUR 2.0 when line items are required
Hourly Cost Explorer data requires opt-in and AWS documents a 14-day availability window. Current-period values are estimated and may update later.
Limits
Know when to leave the console
Cost Explorer resource-level coverage and retention vary by feature. A usage-type increase establishes billed usage, not the team or deployment responsible. Join it to tags, inventory, topology, and change records.
Kulshan
Automate the baseline, keep the question human
kulshan report uses Cost Explorer for its default cost pack. When the question needs deeper billing evidence, the analysis commands work from CUR/Data Exports instead of pretending the summary contains fields it does not.
Keep reading