Cloud Pricing Explained: How AWS, Azure and GCP Actually Charge You
How Cloud Billing Works
Cloud providers measure consumption at the resource level — each virtual machine, gigabyte of storage, and gigabyte of data transferred generates a separate line item on your monthly invoice. AWS, Azure, and GCP all use a pay-per-use model billed in arrears: you consume resources throughout the month and receive an invoice at the end of the billing period.
The fundamental unit of cloud billing is the vCPU-hour for compute and the GB-month for storage. A single m5.xlarge instance (4 vCPU, 16 GB RAM) running for 730 hours in a full month generates 4 × 730 = 2,920 vCPU-hours of consumption. At AWS US East on-demand rates of approximately $0.192/hr, this produces a compute bill of $140.16 before any OS licensing, storage, or networking charges.
Understanding this granular metering is critical because enterprise cloud bills often contain dozens or hundreds of line items. A typical mid-size deployment might include charges for EC2 instances, EBS volumes, S3 storage (multiple tiers), data transfer, CloudFront CDN, Route 53 DNS, RDS databases, EKS control planes, NAT gateways, Elastic Load Balancers, CloudWatch metrics and logs, and support plan fees.
The 4 Pricing Models
Every major cloud provider offers four distinct pricing models for compute resources. Understanding when to apply each model is the single most impactful cost optimization lever available to cloud architects.
| Model | Discount vs On-Demand | Commitment | Best For |
|---|---|---|---|
| On-Demand | 0% | None | Development, testing, unpredictable workloads |
| 1-Year Reserved | ~35% off | 12 months | Stable production workloads with predictable usage |
| 3-Year Reserved | ~55% off | 36 months | Long-running core infrastructure, databases |
| Spot / Preemptible | ~70% off | None — interruptible | Batch jobs, CI/CD pipelines, stateless workers |
On-Demand Pricing
On-demand instances are billed per second (AWS, GCP) or per minute (Azure) with no upfront cost and no long-term commitment. This model is ideal for workloads that are irregular, unpredictable, or short-lived. The major drawback is cost: on-demand is the most expensive pricing model by a significant margin.
For enterprise workloads running continuously in production, operating entirely on on-demand pricing is wasteful. A common pattern is to maintain a baseline reserved fleet covering your minimum predictable capacity, while using on-demand instances to cover demand spikes beyond that baseline.
Reserved Instances
Reserved Instances (RIs) represent a billing commitment in exchange for a significant discount on the hourly rate. You commit to a specific instance type in a specific region for 1 or 3 years. AWS offers three payment options: All Upfront (maximum discount), Partial Upfront (moderate discount plus reduced hourly rate), and No Upfront (lower discount but no capital outlay).
The financial impact of Reserved Instances is substantial. A fleet of 50 m5.xlarge instances running 24/7 at US East on-demand rates costs approximately $9,600/month or $115,200/year. The same fleet on 3-year No Upfront Reserved pricing costs approximately $4,320/month — a saving of $63,360 annually. Over three years, the total saving exceeds $190,000.
AWS introduced Convertible Reserved Instances which allow you to exchange one RI for another of equal or greater value, providing flexibility to change instance families, operating systems, or tenancy during the term. This is recommended for most enterprise deployments as instance families evolve over 3-year periods.
Spot and Preemptible Instances
Spot Instances (AWS), Spot VMs (Azure), and Preemptible VMs (GCP) leverage unused cloud provider capacity at discounts of 60–90% below on-demand pricing. The critical caveat is that these instances can be interrupted with 2 minutes notice (AWS) or 30 seconds (GCP) when the provider needs the capacity back.
Despite the interruption risk, spot instances are extremely valuable for the right workload classes. Batch data processing jobs, machine learning training runs, CI/CD build workers, rendering farms, and genome sequencing pipelines can all be designed to tolerate interruptions using checkpointing and job retry logic. Engineering teams running ML training on spot instances commonly report 70–80% reduction in AI infrastructure costs.
Savings Plans
AWS Savings Plans and Azure Savings Plans are a more flexible alternative to Reserved Instances. Instead of committing to a specific instance type, you commit to a dollar amount of compute usage per hour. Compute Savings Plans apply across EC2, Fargate, and Lambda; EC2 Instance Savings Plans apply to a specific instance family in a region with slightly higher discounts.
GCP offers Committed Use Discounts (CUDs) for 1 or 3-year commitments on vCPUs and memory, and Sustained Use Discounts that are applied automatically (no commitment required) when a resource runs for more than 25% of a month.
Hidden Cost Factors
Beyond compute and storage, enterprise cloud bills contain numerous secondary cost categories that are frequently underestimated during architecture planning:
- NAT Gateway: $0.045/hr plus $0.045/GB processed. A single NAT Gateway handling 100TB/month costs approximately $4,833/month — a major cost driver for private subnet architectures.
- Inter-AZ data transfer: $0.01/GB in each direction. Multi-AZ application architectures that constantly replicate data between availability zones can generate thousands of dollars per month in inter-AZ charges.
- Elastic IP addresses: AWS charges $0.005/hr for Elastic IPs not attached to a running instance. At scale, unattended EIPs become measurable waste.
- CloudWatch Logs retention: $0.50/GB ingested plus $0.03/GB/month stored. Verbose application logging without log retention policies can generate significant unexpected costs.
- Data API calls: S3 PUT, COPY, POST, and LIST requests cost $0.005/1,000 requests. High-frequency microservices making millions of S3 API calls per day can generate hundreds of dollars monthly in API charges alone.
Official Provider Calculators
While this estimator provides accurate planning-level estimates, always validate final architecture decisions against the official pricing calculators before committing:
- AWS Pricing Calculator: calculator.aws — supports all services, regions, and pricing models with detailed configuration options.
- Azure Pricing Calculator: azure.microsoft.com/pricing/calculator — includes Dev/Test pricing and hybrid benefit calculations.
- Google Cloud Pricing Calculator: cloud.google.com/products/calculator — includes sustained use discount calculations and committed use projections.
Ready to estimate your cloud costs?
Use our free estimator to calculate and compare costs across AWS, Azure and GCP with real-time pricing across 130+ global regions.
📊 Open the Cloud Estimator →