Companies often choose the cloud for transparent costs and are then surprised by the first bill. The reason is usually not the provider’s prices but how the costs were estimated and how resources are managed. NIST lists measured service among the essential characteristics of the cloud: resource usage is metered, and both the provider and the customer can see it. That is a chance to keep costs under control, but only if someone actually does it.
Below: what a cloud bill is made of, how to compare it with your own servers, which payment models exist and how not to overpay after the migration.
What the bill is made of
| Item | How it is billed | Watch out for |
|---|---|---|
| Compute | for the time virtual machines run: in AWS, by the hour or by the second | size machines to their actual load, not “the way it was in the server room” |
| Storage | by volume | disks, snapshots and backups are billed separately and add up unnoticed |
| Traffic | inbound is usually free, outbound is billed by volume | AWS and Azure give 100 GB of outbound traffic a month free; after that you pay for every gigabyte |
| Network | VPN gateways, private connections, public IP addresses | an Azure VPN gateway is billed by the hour plus outbound traffic |
| Licences | included in the machine price or your own | Windows Server and SQL Server in the cloud can be paid for with the machine, or you can bring existing licences |
| Support | depends on the plan | providers’ extended support plans are paid |
How to compare with your own servers
For a fair comparison, count the full cost of your own infrastructure, not just the price of a server:
- hardware and its replacement after a few years;
- electricity, UPS and a generator — see “Blackouts: how to keep business IT running”;
- premises, cooling, internet links;
- licences and subscriptions;
- backups and a standby site;
- administrators’ time.
Compare like with like. A server in a back room with no redundancy and a cloud machine with backups and a second site are different levels of availability. Set the same recovery time (RTO) and acceptable data loss (RPO) for both, and only then compare prices. How to define them — see “Disaster recovery: RTO, RPO and a recovery plan”.
AWS and Azure have pricing calculators for estimating the cloud option. Put in more than just the machines: storage, backups, traffic and licences too. Not everything has to move: stable systems on recently purchased hardware can stay in a private cloud — see “Hybrid cloud: what it is and when you need it”.
Payment models
- Pay-as-you-go. No commitment: you pay while a resource runs. The most flexible and the most expensive per hour.
- A one- or three-year commitment. In AWS these are Savings Plans — you commit to a specific amount of usage per hour for one or three years. In Azure, reservations for one or three years, paid up front or monthly. These suit workloads that run all the time. An Azure reservation discounts compute only — Windows licences, networking and storage are paid separately.
- Your own licences. Azure Hybrid Benefit lets you use existing Windows Server and SQL Server licences with active Software Assurance or a qualifying subscription, so you don’t pay for the licence a second time in the machine price. Windows Server needs at least 8 core licences for each machine. For SQL Server, Microsoft gives 180 days during which the licence can be used both on premises and in Azure — for the duration of the migration.
Buy commitments once a workload has settled and you know its real size. Otherwise you may pay up front for resources that turn out to be unnecessary.
How not to overpay after the migration
- Size to actual use. After a few weeks of running, review machine utilisation and shrink the ones that sit idle.
- Turn off what doesn’t need to run around the clock. AWS gives an example: test environments are used about 40 hours a week out of 168. Stopping them outside working hours can cut their compute costs by 75%.
- Clean up what was forgotten. Disks from deleted machines, old snapshots, unused IP addresses.
- Tag resources and assign owners. Tags with the system name and the person responsible let you attribute costs to systems and departments — AWS lists this among its cost optimisation principles.
- Set up budgets and alerts. In Azure, a budget sends an alert when actual or forecast costs cross a set threshold. But it doesn’t stop resources, and cost data is updated with a delay of up to a day. A budget is a signal, not a safety switch.
- Review the bill regularly. Monthly, with IT and finance together: what went up, why, and what can be optimised.
FinOps: costs as a process
The FinOps Foundation describes FinOps as an operational framework and cultural practice that maximises the business value of technology. It rests on shared responsibility for costs between engineering, finance and the business. The FinOps cycle has three phases: inform (see who spends what), optimise (cut the excess) and operate (build it into regular processes).
A small company doesn’t need a dedicated FinOps team. A cloud cost owner, tags on resources, budgets with alerts and a monthly review of the bill are enough.
Common mistakes
- Moving machines “one to one” with sizes set with plenty of headroom.
- Counting only machines and forgetting storage, backups, traffic and licences.
- Buying a three-year reservation before the workload has settled.
- Not bringing existing licences and paying for them twice.
- Treating a budget as a safety switch that will stop spending.
- Having no owner for the cloud bill.
Checklist
- The full cost of your own infrastructure has been calculated
- The cloud option was estimated with the same RTO and RPO requirements
- Storage, backups, traffic, licences and support are in the estimate
- You have checked whether existing licences can be brought along
- Resource sizes were reviewed after the first weeks of running
- Test environments are turned off outside working hours
- Resources are tagged with the system name and owner
- Budgets and alerts are set up
- The bill is reviewed every month
How Bereg-IT can help
We record your current infrastructure costs and compare them with cloud options under the same availability and redundancy requirements. We suggest a payment and licensing model and explain what is worth moving to a public cloud and what to keep in a private one. After the migration we support and optimise your cloud: resource sizes, schedules, budgets and alerts. More on the cloud solutions page; you can start with a consultation or an audit. The move itself is described in “Cloud migration: a step-by-step plan for business”.
The first consultation is free. Send a request and we’ll work out what the cloud would cost you.
Sources
- NIST SP 800-145, The NIST Definition of Cloud Computing (2011) — measured service as a characteristic of the cloud: https://csrc.nist.gov/pubs/sp/800/145/final
- AWS, Amazon EC2 On-Demand Pricing — per-second billing, 100 GB of outbound traffic a month: https://aws.amazon.com/ec2/pricing/on-demand/
- Microsoft Azure, Bandwidth pricing — free inbound traffic, 100 GB of outbound a month: https://azure.microsoft.com/en-us/pricing/details/bandwidth/
- Microsoft Learn, About Azure VPN Gateway — gateway pricing: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
- AWS, What are Savings Plans?: https://docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html
- Microsoft Learn, What are Azure Reservations?: https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/save-compute-costs-reservations
- Microsoft Learn, Explore Azure Hybrid Benefit for Windows VMs: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/hybrid-use-benefit-licensing; Azure Hybrid Benefit — Azure SQL Database & SQL Managed Instance: https://learn.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit
- AWS Well-Architected Framework, Cost Optimization Pillar — Design principles: https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/design-principles.html
- Microsoft Learn, Create and manage budgets — budgets and alerts in Azure: https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-acm-create-budgets
- FinOps Foundation, FinOps Framework: https://www.finops.org/framework/