A cloud bill is unlike other business costs. Nobody approves each item. Engineers switch things on, usage grows, and the invoice arrives a month later. A finance director who would question a RM500 expense claim often has no view of a hosting bill many times that.
You do not need to read every line. You need to know what a healthy bill looks like, what makes one grow, and which controls to ask for.
What you are paying for
Almost every cloud bill for a business system comes down to five things.
- Compute. The servers or services running your application.
- Database. Usually the largest single item for a business system.
- Storage. Files, documents, backups.
- Data transfer. Traffic leaving the cloud, and traffic between components.
- Managed extras. Monitoring, security tools, AI services, email.
Ask your engineer or vendor for the bill grouped under those headings. If they cannot produce that in a few minutes, nobody is watching it.
What a healthy bill looks like
It is boring. It moves a little from month to month, in step with usage. Sudden jumps have an explanation someone can give.
It is proportionate. An internal system used by thirty staff should not cost what a consumer app with a hundred thousand users costs. Small systems run comfortably on small bills. We deliberately choose services that scale down as well as up, so a quiet system is a cheap one.
It has an owner. One named person who sees it monthly and can explain each heading.
Five things that inflate a bill
1. Capacity nobody uses. Servers sized for a peak that never came, running all night and every weekend. Test and staging environments left on permanently. The fix is to size from measured usage, and to switch off what is idle.
2. Things nobody remembers creating. A database from an abandoned experiment. Old backups kept forever. Unattached storage. A quarterly clean-up usually finds some.
3. Data transfer surprises. Moving data out of the cloud, or between regions, is charged. A design that copies large files back and forth can cost more in transfer than in compute.
4. Managed services added by default. Every extra has a monthly minimum. Individually small, together significant.
5. Consumption-priced AI. AI models are billed by the amount of text processed. A feature that costs little in a trial can cost a great deal in production if nobody estimated the volume. Ask for cost per task, multiplied by tasks per month.
The expensive surprise: someone else’s usage
The largest bills we have seen were not caused by the business at all.
When a cloud access key leaks, attackers use the account for their own purposes. Running AI models is now a common one. We handled a case where this began at 11 at night. Charges accrued before anyone was awake.
In that case we helped the client register for a paid support plan, document what had happened and show AWS the evidence that the usage was unauthorised and the account had been secured. The charges were waived. That outcome is at the provider’s discretion, and nobody should rely on it.
Prevention costs almost nothing:
- No long-lived access keys. People sign in with a second factor.
- Services you do not use are blocked outright, including AI model hosting.
- Activity is limited to the regions you operate in.
Four controls every owner should insist on
1. A budget with alerts. A monthly budget per account, with a warning at 80% and at 100%. Note that a budget warns. It does not stop spending.
2. Anomaly alerts. A daily check for unusual jumps, sent to a person who reads email at the weekend.
3. The account in your name. The cloud account should be registered to your company, with your company holding the highest-level credentials. Not your developer’s personal account. Not an agency’s.
4. A monthly one-line report. Total, change from last month, and the reason for any change over 10%.
Questions to ask this week
- What did we spend last month, under the five headings?
- Who receives the alert if spending doubles overnight?
- Whose name is on the account?
- What is running that we could switch off?
- If we use AI services, what does one task cost?
The principle
Cloud spending should be decided, not discovered. A system built with cost in mind from the start is cheaper to run for its whole life. One built without it is cheap only until someone looks.