AWS bill line item
EarlyDelete-ByteHrs
A prorated penalty for an object in S3 Glacier Flexible Retrieval that you delete, overwrite, or transition before its 90-day minimum storage commitment ends. The Instant Retrieval and Deep Archive classes have parallel early-delete charges.
S3 Glacier early-deletion charge
Verified against official AWS documentation last checked
Why it shows up
This is one of the least expected line items on an S3 bill. A lifecycle rule archives to Glacier. A second rule then expires or re-transitions the object in under 90 days. That combination triggers this charge automatically, with no confirmation step.
AWS calculates the charge at the Glacier storage rate for the remaining days of the commitment. It can bill close to the full commitment period, even if the object sat there only briefly. That turns an intended archive-to-save move into a net loss.
How to cut it
- Align lifecycle/expiration policies so objects won't be deleted or re-transitioned before the class's minimum duration (90 days for Glacier Flexible/Instant Retrieval, 180 for Deep Archive).
- Don't archive data you expect to delete or reprocess within the next few months.
- Audit lifecycle rule chains for conflicts, such as an expiration rule shorter than a transition rule's storage-class minimum.
- Run storage-class analytics before enabling archive transitions to confirm the data's real deletion/access horizon.
How to read a usage type
EarlyDelete-ByteHrs carries no region or direction token, so there's nothing to break down here.
Source
Source: AWS docs →Found EarlyDelete-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.