# AWS cost per resource: what each instance, database and NAT gateway costs a month

A tool in the CloudConsole app for iPhone and Android · read-only · free for one account

**Short answer**

Cost Explorer shows cost by service, not by resource, unless you turn on resource-level data. CloudConsole works it out from the other side: it lists your EC2 instances, unattached EBS volumes, RDS databases, NAT gateways, load balancers, Lambda functions and Fargate services, prices each one from the AWS Price List at your region’s on-demand rate (plus the last 7 days of usage where the price depends on it), and ranks them most expensive first.

Screenshot: Cost by resource: $1,689.37 a month estimated for 25 resources in eu-west-2, compared with Cost Explorer, then orders-db and an unattached io1 volume at the top

Screenshot: Monthly cost card on an EC2 instance: m6i.large instance hours, a 50 GB gp3 volume and a $12.12 a month Graviton saving

Screenshot: Waste finder: unattached EBS volumes and idle Elastic IPs with their monthly cost

## What it checks

Open **Services → Tools → Cost by resource**. It covers the resources that make up most of a typical compute bill, in the current region or, with **All regions**, every enabled region:

| Resource | What the estimate adds up |
|---|---|
| EC2 instance | 730 instance hours for its type, platform and tenancy; each attached EBS volume by type and size, with IOPS and throughput above what is included; its public IPv4 address. A stopped instance shows $0 for compute, but its volumes are still billed. |
| Unattached EBS volume | Storage, plus provisioned IOPS and throughput (io1, io2, and gp3 above 3,000 IOPS and 125 MiB/s). |
| RDS database | Instance hours, Single-AZ or Multi-AZ, storage by type and gp3 extras. MySQL, PostgreSQL, MariaDB and Aurora instance hours; Oracle, SQL Server and Db2 aren’t estimated because their price depends on the licence. |
| NAT gateway | Hours plus data processed: the bytes it handled over the last 7 days, scaled to a month. |
| Load balancer | Hours plus LCUs from `ConsumedLCUs` over the last 7 days. |
| Lambda function | Requests, GB-seconds at its memory and architecture, and ephemeral storage above 512 MB, from 7 days of Invocations and Duration. The free tier is shared across the account, so the price is shown before it. |
| ECS service on Fargate | vCPU, memory, Windows licence and extra ephemeral storage for the task size, times the tasks running now. Fargate Spot isn’t in the Price List, so Spot services show the on-demand price as an upper bound. |

Tap any row to open the resource; its own screen carries the same **Monthly cost card**, one line per part of the price. Two savings are worked out where they apply: the same size on AWS Graviton (for example m6i.large → m7g.large, or t3 → t4g) and gp2 → gp3 for EBS volumes, keeping gp2’s baseline IOPS. Next to the total, the tool shows Cost Explorer’s month to date and forecast for the whole account. They won’t match, and it says why: the estimate is list prices for these resources only, while your bill has every service, data transfer, Savings Plans, Reserved Instances, credits and tax.

The [Waste finder](https://cloudconsole.dev/help/waste-finder), next to it in Tools, does the opposite job: it lists what costs money for nothing, such as unattached volumes, idle Elastic IPs and old snapshots.

## How it works, and what it can read

Prices come from the AWS Price List Query API for the resource’s own region and are kept on the phone for 7 days. Usage-based lines read CloudWatch metrics for the last 7 days. The Cost Explorer comparison is one request, cached like the Billing screen’s, because AWS charges $0.01 for each Cost Explorer API request; Price List calls are free.

| What it reads | IAM actions |
|---|---|
| Prices | `pricing:GetProducts` |
| Usage (NAT bytes, LCUs, Lambda invocations and duration) | `cloudwatch:GetMetricData` |
| The resources | `ec2:DescribeInstances`, `ec2:DescribeVolumes`, `rds:DescribeDBInstances`, `ec2:DescribeNatGateways`, `elasticloadbalancing:DescribeLoadBalancers`, `lambda:ListFunctions`, `ecs:ListServices` |
| Month to date and forecast | `ce:GetCostAndUsage` |

Without `pricing:GetProducts` (it is in `ReadOnlyAccess` but not `ViewOnlyAccess`) the card says *Unavailable — needs pricing:GetProducts*. A kind of resource your role can’t list goes under *Couldn’t check*, with the permission it needs, and the rest still show.

All of these reads are in the AWS managed `ReadOnlyAccess` policy. `ViewOnlyAccess` leaves some out; [Recommended permissions](https://cloudconsole.dev/help/recommended-permissions) lists the extras. If one call is denied, the rest of the tool still works and says which permission is missing.

**Nothing leaves your phone.** The app signs each request with your own credentials, which stay in the iOS Keychain or Android Keystore, and sends it straight to AWS. There is no CloudConcur server in between, so we never see your resources or the results.

**Free to look, Pro to fix.** Every check only reads, so it works on the free plan (one account) and in the built-in demo. Where the tool offers a fix, it is the app’s usual action: it needs [Pro](https://cloudconsole.dev/help/free-and-pro), goes through the confirmation you set for that account and is recorded in the activity log on your phone.

## Do it without the app

Two ways, both slower. Cost Explorer can group by resource once you turn on resource-level data in its preferences; it then covers the last 14 days, needs a filter, and is billed at $0.01 a request like other Cost Explorer calls:

```
aws ce get-cost-and-usage-with-resources \
  --time-period Start=2026-11-03,End=2026-11-17 \
  --granularity DAILY --metrics UnblendedCost \
  --filter '{"Dimensions":{"Key":"SERVICE","Values":["Amazon Elastic Compute Cloud - Compute"]}}' \
  --group-by Type=DIMENSION,Key=RESOURCE_ID
```

Or price a resource yourself from the Price List, which only answers in `us-east-1`, `eu-central-1` and `ap-south-1`. This returns the Linux on-demand product for an m7g.large in London; the hourly rate is inside its `terms.OnDemand`:

```
aws pricing get-products --region us-east-1 --service-code AmazonEC2 \
  --filters Type=TERM_MATCH,Field=instanceType,Value=m7g.large \
            Type=TERM_MATCH,Field=regionCode,Value=eu-west-2 \
            Type=TERM_MATCH,Field=operatingSystem,Value=Linux \
            Type=TERM_MATCH,Field=tenancy,Value=Shared \
            Type=TERM_MATCH,Field=preInstalledSw,Value=NA \
            Type=TERM_MATCH,Field=capacitystatus,Value=Used \
  --max-results 1
```

Then multiply by 730 hours and repeat for every volume, gateway and function. Tagging resources and activating cost allocation tags is the long-term answer for teams: it puts owners, not resource IDs, on the bill.

Related free tool on this site:

- [EC2 cost calculator](https://cloudconsole.dev/tools/ec2-cost-calculator) (free, in your browser)
- [RDS cost calculator](https://cloudconsole.dev/tools/rds-cost-calculator) (free, in your browser)
- [Lambda cost calculator](https://cloudconsole.dev/tools/lambda-cost-calculator) (free, in your browser)
- [Fargate pricing calculator](https://cloudconsole.dev/tools/fargate-pricing-calculator) (free, in your browser)

## Questions

### Why is the total different from my AWS bill?

The estimate covers seven kinds of resource at on-demand list prices, with usage from the last 7 days scaled to a month. Your bill also includes every other service, data transfer, Savings Plans, Reserved Instances, credits and tax, and it is for real usage, not an extrapolation.

### Does it use my region’s prices?

Yes. Each resource is priced for its own region from the AWS Price List. The free web calculators on this site use us-east-1 prices; the app uses the region the resource is in.

### Does it include S3?

No. S3 cost depends on storage class, requests and transfer per bucket, which the Price List can’t tie to a bucket without usage data. The Billing screen shows S3 spend by usage type, and the S3 bucket audit lists buckets without lifecycle rules.

### Can it change anything?

Only through the buttons it shows: Change to gp3 on a gp2 volume, and Change class with the Graviton class picked on RDS. Both are Pro changes with your confirmation. Looking is free.

## Try it on your own account

CloudConsole is on the App Store for iPhone and Google Play for Android. Every tool also works in the built-in demo, if you’d rather look around before connecting an account.

[Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710) · [Get it on Google Play](https://play.google.com/store/apps/details?id=com.cloudconsole.app) · [Getting started guide](https://cloudconsole.dev/help/getting-started)

Details: [Tools for your AWS account](https://cloudconsole.dev/help/tools) in the help centre.

## Related

- [How to see an AWS cost breakdown](https://cloudconsole.dev/how-to/see-aws-cost-breakdown) – How-to guide
- [What is "EC2 - Other" on my AWS bill?](https://cloudconsole.dev/costs/ec2-other-costs) – AWS cost guides
- [Why is my NAT Gateway bill so high?](https://cloudconsole.dev/costs/nat-gateway-cost) – AWS cost guides
- [gp2 vs gp3 cost](https://cloudconsole.dev/costs/gp2-vs-gp3-cost) – AWS cost guides
- [EC2 cost calculator](https://cloudconsole.dev/tools/ec2-cost-calculator) – Free tools
- [See what each resource costs](https://cloudconsole.dev/help/resource-costs) – Help centre

---

Source: https://cloudconsole.dev/app-tools/aws-cost-per-resource

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
