AWS bill line item
TimedStorage-GlacierByteHrs
GB-month storage charge for archived objects held in the S3 Glacier Flexible Retrieval class, AWS's low-cost long-term archive tier.
S3 Glacier Flexible Retrieval storage
Verified against official AWS documentation last checked
Why it shows up
Glacier's low per-GB rate is the headline. It also carries a 90-day minimum storage commitment. Separate per-GB retrieval fees apply, and they differ widely by speed tier. They show up on other bill lines, not this one.
Lifecycle policies that archive data too early can turn a storage saving into a net cost increase. Logs that a job still queries monthly are an example. Retrieval and early-delete charges add the cost back.
How to cut it
- Archive only data confirmed cold via access logs or storage-class analytics before writing the lifecycle rule.
- Use the slowest acceptable retrieval speed whenever the restore isn't time-critical; the price gap between tiers is large.
- Ensure archived objects will sit at least 90 days to avoid the early-deletion charge.
- For rarely-touched, longer-horizon data, compare against Deep Archive's lower rate (with a longer minimum and retrieval time).
How to read a usage type
TimedStorage-GlacierByteHrs carries no region or direction token, so there's nothing to break down here.
Source
Source: AWS docs →Found TimedStorage-GlacierByteHrs 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.