What managed AWS hosting actually includes, and what's still on you
What managed AWS hosting includes, and what stays on you: patching, backups, monitoring, and the account, app, data and access decisions you still own.
·
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.
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.
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.
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.
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.
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.
What managed AWS hosting includes, and what stays on you: patching, backups, monitoring, and the account, app, data and access decisions you still own.
·
4 min read
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
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
Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.
·
3 min read
When you need Terraform (and when you don’t): honest triggers for IaC vs console, scripts, or managed PaaS.
·
3 min read
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
What to check before you inherit a custom app: code and deploy-key control, tests, patches, and whether a fix can ship tomorrow.
·
4 min read
What a website quote should include beyond the build: hosting, domain ownership, care and who fixes the site at 2am.
·
4 min read
When the office broadband dies and nobody has a backup, work stops. What fails, why a hotspot is not a plan and what tested failover looks like.
·
3 min read
The agency that built your website has disappeared. How to recover access, move hosting and DNS into the business, and choose care or a rebuild.
·
4 min read
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
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
If your website form still emails one person's Gmail, enquiries vanish when they're away, and a shared lead list with an owner fixes it.
·
4 min read
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
Who actually owns your business domain name? How to check the registrant and account holder, and move both into company hands.
·
4 min read
What the NCSC's China-linked botnet alert means for a small business: check the router and remote access kit you already own.
·
4 min read
GDPR and cookies on a small business website: when cookies need consent under the 2026 rules, and how long to keep contact form data.
·
4 min read
The info@ inbox nobody owns is where a UK SME's enquiries sit with no named owner and no reply time.
·
4 min read
How to approach moving off Wix or Squarespace without losing your Google ranking, from exporting content to setting up 301 redirects.
·
4 min read
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