Cloud read costs
What AssetHermit's own reads cost in your clouds: every call your providers bill, at list price, by month and source.
AssetHermit only reads your clouds, and most of what it reads is free. Some reads your providers bill to your own account: queries over a billing export in BigQuery, metrics read from CloudWatch, log queries, files read from your storage. We call these read costs. Every read that bills you adds what it used to a ledger in your workspace, so you can see what AssetHermit costs you in your clouds, not only what you pay us.
Open Workspace settings → Cloud read costs to see this month and the 12 months before it, by feature (Cost import, Carbon, Usage metrics, Uptime reads, Log queries, Log analyses, IaC sources, Your assistant model) and by source, each line with how it's known. The ledger keeps 400 days. Workspace Admins and members who see costs across the whole workspace see it.
How figures are counted
- At list price, before free tiers and discounts. A free tier is shared with everything else on your billing account, and your discounts are your contract, so the figure is what the provider's price page says. Your bill may be lower.
- Every read that billed you counts, whether or not its run succeeded. A task stopped before it finishes loses its count, so figures are at least what's shown.
- Measured, counted or estimated. Each line says which: the provider reported what it billed, we counted the units it bills by, or the price depends on something we can't know for sure, such as a bucket's region.
- Figures are shown in your workspace's reporting currency, converted at the latest ECB reference rate.
What bills you
| Cloud | What bills it | List price | How it's known |
|---|---|---|---|
| AWS | Amazon S3, GET requests | $0.40 per million requests | Counted: we count the units it bills by |
| AWS | Amazon S3, LIST requests | $0.005 per 1,000 requests | Counted: we count the units it bills by |
| AWS | Amazon S3, data transfer to another region | $0.020 per GB | Estimated: the price depends on what we can't know |
| AWS | Amazon CloudWatch, metrics requested (GetMetricData) | $0.010 per 1,000 metrics | Counted: we count the units it bills by |
| AWS | CloudWatch Logs Insights, bytes scanned | $0.005 per GB | Measured: the provider says what it billed |
| AWS | Amazon Athena, data scanned | $0.005 per GB | Measured: the provider says what it billed |
| AWS | Amazon Bedrock, tokens | The model's Bedrock price per token | Measured: the provider says what it billed |
| Google Cloud | BigQuery, bytes billed by queries | $0.0057 per GB1,100 GB free a month | Measured: the provider says what it billed |
| Google Cloud | Cloud Monitoring, time series returned | $0.50 per million series1,000,000 free a month | Counted: we count the units it bills by |
| Google Cloud | Cloud Storage, data transfer out | $0.12 per GB | Estimated: the price depends on what we can't know |
| Azure | Azure Storage, data transfer out | $0.087 per GB100 GB free a month | Estimated: the price depends on what we can't know |
| Azure | Azure Monitor, metric calls | $0.010 per 1,000 calls1,000,000 free a month | Counted: we count the units it bills by |
| Azure | Azure Monitor Logs, Basic and Auxiliary tables scanned | $0.005 per GB | Estimated: the price depends on what we can't know |
Amazon S3 reads from a bucket in your workspace's region go through a gateway endpoint and bill no data transfer; only the requests count. A bucket in another region bills the bytes read as data transfer between regions.
What's free
- AWS: Describe, List and Get calls the asset collector makes (EC2, IAM, Lambda and the others)
- AWS: CloudTrail event history (LookupEvents), for cloud activity
- AWS: AWS Organizations, CloudFormation, Service Quotas and the Sustainability API
- AWS: KMS and Secrets Manager Describe and List calls, S3 bucket configuration reads (billed, a fraction of a cent a run)
- AWS: The provider health stack's log group, a few kilobytes a month (billed, a fraction of a cent a run)
- Google Cloud: Cloud Asset Inventory and Resource Manager, for the inventory
- Google Cloud: Recommender's firewall insights
- Google Cloud: Cloud Logging's entries.list, for cloud activity and log queries
- Google Cloud: Personalized Service Health and Advisory Notifications
- Google Cloud: BigQuery dry runs, for estimates and permission checks
- Azure: Azure Resource Graph: resources, changes and service health
- Azure: Azure Resource Manager reads, such as diagnostic settings
- Azure: Log Analytics queries over Analytics tables
- Azure: Carbon Optimization reports
Finding our queries in your bill
Every BigQuery job AssetHermit runs in your Google Cloud project carries two labels, which your billing export keeps on the job's rows: assethermit, saying what it's for, and workspace, the workspace's ID. Filter your billing export, or a cost report over it, by the assethermit label to see what our queries were billed.
| Label | The job is |
|---|---|
assethermit=cost-collector | importing your billing export |
assethermit=carbon | reading your Carbon Footprint export |
assethermit=log-query | a log query someone ran, or the assistant ran for them |
assethermit=log-analysis | a weekly log analysis |
AWS and Azure bills don't say who made a call. In AWS CloudTrail, AssetHermit's calls are made by roles whose names start with asset-hermit-, under the path /ah/.