Home
›
Articles
›

Why your AWS bill and your management fee are two different bills

Why your AWS bill and your management fee are two different bills

By Ibi Hasanli

·

·

4 min read

Your AWS bill and your management fee are two different bills, and they move for different reasons. The AWS invoice is usage: compute, storage, data transfer, snapshots and logs, and it can rise with traffic or growth even if the care arrangement does not change. The management fee should pay for agreed operational work, not for the underlying AWS usage itself.

What the management fee should pay for

A monthly fee is payment for someone to look after the environment, on terms you can point to. What that work should include, and what stays on you, is the subject of what managed AWS hosting actually includes, and what's still on you. This piece is about the money.

In a good arrangement, the fee pays for agreed care: patching, backups, monitoring and alerts, and someone to act when a threshold is crossed. At Eight Mile, infrastructure support can include patching, backups and on-call cover, through a monthly arrangement with agreed coverage. Under a support retainer, monitoring can cover uptime, errors and cost, with an engineer alerted when a threshold is crossed. Our infrastructure work also includes backups tested by restoration.

Ongoing restore testing, the exact shape of incident response, and small changes are not automatic extras in that fee. Get them in writing if you need them, including what counts as a small change and what is billed separately. Out-of-hours cover is part of the retainer only if it is written down. Ordinary enquiries are handled during London business hours, Monday to Friday.

Two bills, two reasons they move The AWS invoice Compute, billed on usage Storage, snapshots and backups Data transfer and logs Traffic spikes and growth This bill can rise even when the management fee stays the same. The management fee Patching, if the retainer says so Backups and monitoring On-call cover in agreed hours Other work only if it is written This fee pays for agreed care, not for the underlying AWS usage. They are two different bills, paid for two different things.
The AWS invoice is usage. The management fee pays for agreed care. They move independently, and only the written retainer decides what the fee covers.

Why the AWS bill moves on its own

Amazon charges for what you use. Compute runs by the hour or by the request. Storage, snapshots and backup copies accumulate. Data transfer and logs have their own lines. A traffic spike, a forgotten disk, or a growing archive can move the invoice without anyone touching the management fee.

That is why a flat care fee is not a cap on AWS spend. If the invoice climbs and nobody can explain it, the usual failure is that usage was not being watched, which we covered in cloud bill went up and nobody can say why.

How to keep the AWS bill more predictable

You will not make usage perfectly flat. You can make surprises rarer. Budgets, billing alerts and resource tagging help you see what is growing, and who it belongs to, before the invoice arrives.

Ask whether those controls are in place, and who watches them. Eight Mile's infrastructure work includes cloud cost reviews, looking for forgotten resources, oversized instances and unsuitable storage tiers. Under a retainer, monitoring can also cover cost. How you will be told about a rising bill, and at what threshold, still belongs in the written arrangement.

Questions to ask before you sign

Before you commit, get answers on paper to the commercial questions, not only the technical ones.

Whose name is the AWS account in? It should be the business's. A provider can work with access to it. They should not take it over. If the root login still sits with a freelancer, start with leaving a freelancer with your AWS root login.

Who pays AWS directly? Get that in writing, because the payer often holds the billing relationship, and leaving is harder if the invoice does not come to you.

What does the management fee include, and what is billed as extra? Small changes, restore tests and out-of-hours work are the usual grey areas.

What are the notice and exit terms? Ask how you leave with the account, the data and a workable handover.

How will cost changes on the AWS invoice be flagged to you? An alert that nobody is contracted to act on is not a cost review.

Ask these before you sign The account Whose name is the AWS account in? Who pays AWS Do you pay Amazon directly, or through the provider? Included What the fee covers, and what is billed as extra Exit Notice, handover and how you leave with the account Cost changes How a rising AWS invoice will be flagged to you Get the answers in writing. A verbal assurance is not an agreement.
Five commercial questions to get answered in writing before you sign, including who pays AWS and how a rising invoice will be flagged.

How Eight Mile charges for infrastructure care

Our infrastructure and cloud work includes designing, building and running infrastructure on AWS. Customers keep the cloud accounts. We work with access to them. After a build, delivered work is covered for twelve months. Ongoing monitoring, patching, backups and on-call support are available through a monthly arrangement with agreed coverage. Support is a separately agreed retainer, sized to what is covered. Billing for scoped work starts only once a written scope and price are agreed.

The useful test is whether your AWS bill and your management fee are shown as two different bills, with a named owner for each. If they are bundled into one vague figure, you will not know which bill moved when something changes.

If you want that split agreed properly, on an AWS account you own, talk to an engineer. Tell us what is running and how you are billed today.

AWS
Infrastructure

Leaving a freelancer with your AWS root login

Leaving a freelancer with your AWS root login is a risk even after a good build. How to take back control with named IAM, MFA and a handoff.

·

4 min read

Infrastructure
Cloud

Moving off the server under the desk

Moving off the server under the desk: stage a move to managed hosting or cloud you own — without a big-bang rewrite.

·

3 min read

Infrastructure
Cloud

Cloud bill went up and nobody can say why

Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.

·

3 min read

AWS
Infrastructure

AWS vs managed hosting for a small SaaS

AWS vs managed hosting for a small SaaS: when simple platforms fit, and when owned cloud, IAM and infra in git win.

·

3 min read

CRM
SaaS

CRM for a small firm off the shelf or built

CRM for a small firm off the shelf or built: when HubSpot-class tools fit, and when a system on your own job data serves trades and clinics better.

·

4 min read

Websites
Hosting

Uptime monitoring for a small business website

Uptime monitoring for a small business website only works with a named engineer and response path. What a care plan or managed hosting should cover.

·

3 min read

TradeOps
SME

When WhatsApp is running your jobs

When WhatsApp is running your jobs, groups and voice notes become the job board. What a proper ops system replaces, without taking phones away.

·

4 min read

Software
Customer service

The info@ inbox nobody owns

The info@ inbox nobody owns is where a UK SME's enquiries sit with no named owner and no reply time.

·

4 min read

AI
Decision models

Jev vs Laya

Jev vs Laya for UK tech leads: when to call TypeSafe's hosted decision API and when to self-host the open-weight Laya model on your own infrastructure.

·

4 min read