Quick Fix:
Grab the AWS Pricing Calculator (it's free) to ballpark your cloud spend before you move anything. That old AWS TCO Calculator? Gone since 2023.
What’s Happening
Total Cost of Ownership (TCO) for cloud isn’t just about the monthly invoice. It’s the full picture—hardware depreciation, electricity, staff time, and the risk of downtime when you run things on-prem versus the pay-as-you-go cloud route. AWS canned its original TCO tool in 2023 and now points everyone to the AWS Pricing Calculator, which is free and lets you build migration cost models on the fly.1
Take a small business with 20 on-prem servers. Power runs about $12,000 a year. Maintenance contracts hit $8,000. Throw in $5,000 for surprise repairs, and you’re staring at $25,000 annually. Move to AWS with 20 t3.medium instances and you’re looking at roughly $1,800 a month ($21,600 a year) once you factor in data transfer. That’s about $4,600 in yearly savings—and you get scalability and uptime guarantees you won’t find in your own data center.
Step-by-Step Solution
- Open the AWS Pricing Calculator Head to calculator.aws.amazon.com. Chrome or Edge work best; Firefox will get the job done but can feel sluggish.
- Create a new estimate Hit “Create estimate,” then “Define your service requirements.”
- Add compute resources
Under “EC2,” click “Add instance type.” Pick:
- t3.medium (2 vCPUs, 4 GiB RAM) for everyday workloads
- Linux/Unix (Amazon Machine Image) unless you’re stuck on Windows
- 1-year Reserved Instance to save about 35% compared to On-Demand
- Include storage
While you’re in the same estimate, toss in:
- Amazon EBS General Purpose SSD (gp3) volumes: 100 GB at $0.08/GB-month
- S3 Standard for backups: 500 GB at $0.023/GB-month
- Add data transfer Under “Data Transfer,” plug in your expected monthly outbound traffic—say, 500 GB to users at $0.09/GB.
- Review and export Click “View estimate.” Download as PDF or share the link. Flip between “On-Demand” and “Reserved” to see the difference.
Pro move: Toggle “EC2 Spot Instances” for dev/test workloads—you can cut costs by up to 90% versus On-Demand.2
If This Didn’t Work
Alternative 1: AWS Cost Explorer
Already running AWS services? Log in to the Cost Explorer. Filter by service (EC2, RDS, Lambda) and timeframe. Check the “Reserved Instance Recommendations” report to spot overspending. One dev team saved $3,200 a year by swapping 10 On-Demand t3.small instances for 2 Reserved Instances and 8 Spot Instances.3
Alternative 2: Third-Party Tools
Tools like CloudHealth by VMware or Cloudability pull in your AWS billing data and map costs to teams or projects. They’re free up to $10,000/month in AWS spend; paid tiers start at $500/month. These tools highlight orphaned volumes, idle instances, and underused resources.4
Alternative 3: Manual Spreadsheet Model
Want full control? Build a TCO sheet with columns like these:
| Cost Item | On-Prem Estimate | AWS Estimate |
|---|---|---|
| Hardware Depreciation | $8,000/year | $0 |
| Software Licenses | $2,400/year | $0 (if you’re using open-source) |
| Power & Cooling | $1,200/year | $0 |
| IT Staff Time (Admin) | 10 hrs/week @ $75/hr | 2 hrs/week @ $75/hr |
| Network Bandwidth | $600/year | $450/year |
| Total (3-Year TCO) | $41,400 | $19,800 |
Just keep in mind: manual models often miss sneaky costs like egress fees or support plans. Run your numbers by AWS Support before you commit.
Prevention Tips
Head off budget surprises with these habits:
- Tag everything Label resources by project, team, or environment (e.g., “prod-web-01”). The AWS Tag Editor can bulk-tag existing resources. Tags make chargeback/showback easy and keep cost allocation simple.5
- Set budget alerts In AWS Budgets, set a $1,000/month cap for the “Dev” team. You’ll get an email or Slack ping when spend hits 80% of the limit. AWS added anomaly detection in 2025 to flag weird spikes automatically.6
- Use AWS Compute Optimizer Fire up the free Compute Optimizer every month. It crunches your EC2 usage and suggests instance families that actually fit your workload (swap an m5.large for a c6g.large if you’re CPU-bound, for example). Users routinely save up to 25% after following its advice.7
- Schedule non-production shutdowns Use AWS Instance Scheduler or EC2 Auto Stop/Start to power down dev/test environments nights and weekends. A $0.04/hour t3.small instance running 24/7 costs about $350/month; shut it down 16 hours a day and you’ll save roughly $230/month.8
Honestly, the AWS Pricing Calculator is your best bet for a realistic, up-to-date TCO estimate. Pair it with Cost Explorer, budgets, and optimization tools, and you’ll keep costs predictable even as your cloud footprint grows.
