Beta

Reports What to change

Other providers

What your AWS setup could cost at Azure, at DigitalOcean or on a cluster of your own, like for like, resource by resource. An estimate, and it says so.

New: the estimate is being checked by hand against the providers' own price calculators for the first companies, and the report says so until it has been.

What it shows

For each service and each resource on your AWS bill, a month at AWS today and a month at each of four columns: Azure, Azure with a one-year reservation, DigitalOcean, and a cluster of your own if you have given it a price per core-hour and GiB-hour. Each resource's row says what it is on AWS today, whether a commitment or spot covers it, and for each column the size it was matched to, the price and how it was priced. A first section shows, per column, how much of the month rests on the provider's price list, how much on a published rate and how much on your own ratio: the larger the part by ratio, the rougher the column.

Not counted: data transfer and egress, backups beyond the free allowance, support plans, the one-time cost of moving (copying the data out, people's time), private and enterprise discounts on the AWS side, and storage on your own cluster. A figure can be off by a size, or by a price change since a rate was read. It is what the same setup could cost about, never what you will save.

Questions it answers

  • What would our AWS setup cost at Azure or DigitalOcean, roughly, service by service?
  • Which of our resources are priced by a real list price elsewhere, and which only by a ratio?
  • What would the same workloads cost on a cluster of our own, at what our hardware costs us?

What it reads

Once a day, what each resource cost on the AWS bill over the last seven whole days, scaled to a month, from the Cost and Usage Report export you connect, at amortized cost with credits left out. Beside it, the providers' own prices by size, read once a day from their price lists, at the closest size, larger or smaller, in the same class where the provider has one (burstable to burstable), with Multi-AZ as the provider's high-availability option; MariaDB and Aurora count as the nearest managed MySQL or PostgreSQL. Where a provider publishes no prices by size, a published rate for what the line is billed by, with the page it was read from and the day. What has no comparable unit, such as a database billed by request, a function or logs, is today's AWS cost times your own ratio over everything priced the first two ways. A column whose prices are more than seven days old shows no figure. A region with no provider region in the same legal area is priced at the nearest region anywhere, and says so.

What to do with it

Use it to put a number on a conversation that otherwise has none: whether a second provider is worth a pilot, or what a cluster of your own would have to cost per core-hour to compete. Read the ratio share first; a column mostly by ratio is a guess dressed as a figure. Nothing is right-sized here, so an oversized instance stays oversized in every column; the savings recommendations are where the sizes are questioned.

Related reports

  • AWS cost from the bill: The settled bill per day, with discounts and the Savings Plan, the month projected from it, and the cost by service and by line item type.
  • AWS savings recommendations: Changes that would cut the bill, priced per month, largest first, and what the changes made so far save.
  • Kubernetes cost: What each namespace and workload costs on your Kubernetes clusters, in AWS and on your own servers, and a month at this rate, by namespace and by cluster.

The hosted plan has every report, and is free during early access: see pricing. Like every report, this one splits and filters by account, environment, service and resource, steps back 13 months, downloads as PDF and CSV and keeps the view in its link: what every report does. All reports.