ask-an-engineer
You can see what changed on the bill. This is where you find out why.
FinOps analysts see the movement before anyone else. Explaining the engineering behind it usually means waiting on a devops team that has other priorities, or going to a manager without an answer.
Send me the question instead. I will write back with the mechanism, the evidence that would confirm it, and what to check next.
This is free. There is no charge, no tier, and no upsell attached to it. Independent consultant or analyst inside a large enterprise, same answer either way.
What this is good for.
- A service line moved and the usual explanations do not fit
- Reserved Instance or Savings Plan coverage behaving in a way that does not match the commitment you bought
- Data transfer, NAT, or inter-AZ charges that appeared without an obvious trigger
- A cost that dropped when you expected it to rise
- Anything where you can describe the shape of the movement but not the engineering that caused it
What to leave out.
Do not send account IDs, Cost and Usage Report extracts, console screenshots, or dollar amounts.
Percentages, service names, and time windows are enough to explain a mechanism. Keeping customer data out of this is deliberate: it means you can ask without routing anything through your own procurement or security review first.
How this works.
- You email me the question.
- It goes into a queue and I answer in order.
- You get a written explanation by email.
- Answers get published on this site with every identifying detail removed, so the next person with the same question finds it.
I answer these between client engagements, so there is no promised turnaround. Current queue is shown below.
Questions are answered in the order received.
Email your question to [email protected].
If the answer turns out to be something finance needs defended in writing, that is a different piece of work and I will say so. Otherwise the answer is the answer.