How to read AWS usage types
A usage type is the exact meter a charge comes from, written as an optional Region billing code followed by the meter name, for example EUW2-NatGateway-Bytes (NAT gateway data processed in eu-west-2) or USE1-TimedStorage-ByteHrs. Group by Usage type in Cost Explorer to see them; the prefix tells you where, the rest tells you what.
The Region prefix
The prefix is an AWS billing code, not the API Region name. The common ones:
| Prefix | Region | Prefix | Region |
|---|---|---|---|
USE1 | us-east-1 | EU | eu-west-1 (Ireland) |
USE2 | us-east-2 | EUW2 | eu-west-2 (London) |
USW2 | us-west-2 | EUC1 | eu-central-1 |
APN1 | ap-northeast-1 | APS1 | ap-southeast-1 (Singapore) |
APS2 | ap-southeast-2 (Sydney) | APS3 | ap-south-1 (Mumbai) |
Two quirks: Ireland is plain EU, and several services (S3, DynamoDB, EC2 data transfer) omit the prefix entirely for us-east-1, so TimedStorage-ByteHrs with no prefix is N. Virginia. Inter-Region transfer uses two codes, source first: USE2-APS3-AWS-Out-Bytes. CloudWatch also uses Global- for some free tier lines.
Common families and what they meter
| Pattern | Service | Meter |
|---|---|---|
BoxUsage:t3.large | EC2 | On-Demand instance hours (detail) |
EBS:VolumeUsage.gp3 | EC2 - Other | Volume GB-month (detail) |
NatGateway-Bytes | EC2 - Other | NAT GB processed (detail) |
DataTransfer-Out-Bytes | Many | Internet egress (detail) |
DataTransfer-Regional-Bytes | Many | In-Region, mainly cross-AZ (detail) |
TimedStorage-ByteHrs | S3, CloudWatch Logs, DynamoDB | Storage over time (S3 detail) |
Requests-Tier1 | S3 | PUT, COPY, POST, LIST requests (detail) |
DataProcessing-Bytes | CloudWatch | Log ingestion (detail) |
PublicIPv4:InUseAddress | VPC | Public IPv4 hours (detail) |
The same suffix can mean different things in different services. TimedStorage-ByteHrs under S3 is Standard storage; under CloudWatch it is log storage. Always read the usage type together with the service.
List the usage types on your bill
# Every usage type with spend this month, most expensive first
aws ce get-cost-and-usage --region us-east-1 \
--time-period Start=2026-11-01,End=2026-11-17 \
--granularity MONTHLY --metrics UnblendedCost \
--group-by Type=DIMENSION,Key=SERVICE Type=DIMENSION,Key=USAGE_TYPE \
--query 'ResultsByTime[0].Groups[].[Keys[0],Keys[1],Metrics.UnblendedCost.Amount]' \
--output text | sort -t$'\t' -k3 -gr | head -25
# Search usage type names
aws ce get-dimension-values --region us-east-1 \
--time-period Start=2026-11-01,End=2026-11-17 \
--dimension USAGE_TYPE --search-string DataTransferEach Cost Explorer API request is charged (a cent per request at the time of writing), so script sensibly rather than looping per day per service.
Operation: the other half of the story
Usage type says what was metered; Operation says which API or feature caused it. For EC2, RunInstances and RunInstances:0002 separate Linux from Windows hours. For S3, PutObject and ListBucket separate writes from listing within the same request usage type. For CloudWatch, PutLogEvents marks log ingestion. Group by both in Cost Explorer when a usage type alone does not explain a change.
Where to look up a usage type you do not recognise
- Many services publish a billing codes page, for example EC2, EBS, S3 and CloudWatch. Search the service documentation for "billing and usage reports".
- The cost and usage export has a
line_item_line_item_descriptioncolumn that spells out the rate in words. - On the Bills page, expanding a service shows the same meters with readable descriptions.
A common mistake is filtering Cost Explorer by Region and missing global lines: some charges have no Region or are billed in us-east-1 regardless of where you work.
Questions
What does EUW2 mean on my AWS bill?
It is the billing code for the eu-west-2 (London) Region. It prefixes usage types for charges incurred there.
Why do some usage types have no Region prefix?
Several services omit the prefix for us-east-1, so a bare usage type such as DataTransfer-Out-Bytes is N. Virginia.
What is a usage type group in Cost Explorer?
A Cost Explorer filter that collects related usage types across Regions, such as EC2: Running Hours or EC2: NAT Gateway - Data Processed.
Usage types are the bit of the bill nobody can read from memory. CloudConsole, a phone app for AWS, shows spend by service and usage type and explains each usage type in plain words, so EUW2-DataTransfer-Regional-Bytes is not a mystery on call.
About the app → · Download on the App Store