AWS bill line item
TimedStorage-ByteHrs
The core "you store data, you pay for it" charge: GB-months of object data and metadata held in S3 Standard storage, billed hourly and averaged over the month.
S3 Standard storage
Verified against official AWS documentation last checked
Why it shows up
It's usually the single largest line on an S3 bill and grows silently: versioning-enabled buckets keep every prior object version, and incomplete multipart uploads consume storage without showing up in a normal object listing.
Because usage is measured in byte-hours but invoiced in GB-months, steady daily upload growth compounds across a billing cycle in a way that's easy to underestimate from a quick console glance. Note: this exact usage-type string is reused by several other AWS services too (DynamoDB and CloudWatch Logs among them). The Service column, not the code alone, tells you which one you're looking at.
How to cut it
- Enable lifecycle rules to expire noncurrent object versions and abort incomplete multipart uploads.
- Use storage analytics to find cold data worth moving to a cheaper storage class.
- Audit versioning-enabled buckets for unbounded historical version growth.
- Compress or dedupe frequently-repeated large objects (logs, build artifacts) before they land in the bucket.
How to read a usage type
TimedStorage-ByteHrs carries no region or direction token, so there's nothing to break down here.
Source
Source: AWS docs →Found TimedStorage-ByteHrs on your own bill?
Drop your Cost Explorer CSV into the AWS Bill Analyzer. It'll flag line items like this one on your own bill and link straight back to the fix.
Analyze your own bill →The meter you don't watch still grows.
Waste rarely hides in the service you check every week. CostMon watches every meter on your stack, including the ones you forgot were running.