Skip to main content

Cost estimates

Where AWS publishes a price, Delegaris shows roughly what a machine costs, so people can see what keeping something on means before they do it.

The figures are estimates from AWS list prices. They are good for comparing and for a sense of scale, not for the bill.

Where you see them​

WhereWhat it says
A machine's details on the Resources pageCost: "About $0.19 an hour while running (on-demand list price, before discounts)"
The same, when the schedule's hours are knownIts schedule saves: "About $22 a week"
The keep-on dialog"Roughly $1.52 at list price" for the time chosen, and "for the 2 with a known price" when only some of the machines have one
The Kept on past schedule reportA Cost for each keep-on, and a total, "roughly $14.20 at on-demand list prices"
The keep-on report's CSVAn Estimated cost (USD) column

How they are worked out​

  • Hourly cost: the on-demand price for that kind of machine in its region. For a Redshift cluster it is the price per node times the number of nodes.
  • What the schedule saves: the hours in a week the schedule has the machine off, times the hourly cost. This needs the schedule's hours under Friendly names, and is not shown for an Always on schedule.
  • A keep-on's cost: the hours chosen (in the dialog) or the hours it actually ran (in the report) times the hourly cost. A keep-on keeps the price it had when it was set.

What is estimated​

EstimatedNot estimated
EC2 instances: Linux or Windows, shared tenancyOracle and SQL Server databases (their price depends on licensing)
RDS instances: PostgreSQL, MySQL and MariaDB, single or Multi-AZAurora, DocumentDB and Neptune clusters (listed as clusters, not as their member instances)
Redshift clusters, per nodeAuto Scaling groups, ECS services, EKS node groups, SageMaker notebooks and Lightsail instances

Anything not estimated simply shows no cost.

What the prices leave out​

Prices are on-demand list prices in US dollars, from the AWS Price List API. They are before:

  • Savings Plans and Reserved Instances,
  • the free tier,
  • any discount your organisation has, and
  • storage, data transfer and anything else charged apart from running time.

How prices are fetched​

Administrators

The service's own AWS identity needs pricing:GetProducts. The standard policy (iam/hub-policy.json) and the iam/hub-role.yaml template include it. See Service identity.

  • The copy of the service doing the timed work looks prices up in the background and keeps each one for a week, so the resource list never waits for them. A kind of machine seen for the first time shows no cost until its price has been looked up.
  • Without pricing:GetProducts there are simply no estimates, and nothing else is affected. The service tries again every few hours, so adding the permission later is enough.
  • If the Price List API cannot be reached, it tries again an hour later.
  • Prices are fetched in US dollars only.