Cloud cost
Storage class
A pricing and durability tier for stored data. The same bytes cost a different amount, and take a different time to read back, depending on the class.
Last updated
Definition
Every major object-storage service offers a ladder of classes. The colder classes trade a lower per-GB storage rate for a longer minimum storage period, a per-GB retrieval fee, or a slower restore. The AWS ladder runs from S3 Standard down through Standard-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive. A wrong pick costs money in either direction. A class that is too hot wastes money on data nobody reads. A class that is too cold adds retrieval fees and early-delete penalties that can erase the saving.
Block storage, such as EBS volumes, has its own ladder with a different shape. It has general-purpose SSD, provisioned-IOPS SSD, and two tiers of HDD. You pay by provisioned size and performance, not by access frequency.
Where it shows up
A storage class appears on the bill as its own billing line. AWS S3 lists Standard, Standard-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive as separate classes. Each has its own per-gigabyte rate. The colder tiers add a retrieval fee on top.
What makes it expensive
The mistake runs in both directions. Data sits in a hot, expensive class that nobody reads. Or data moves to a cold class before its minimum storage duration ends, and an early-delete penalty applies. Both look the same on an undifferentiated storage line. Report storage by class. Then read each class against how often that data is touched.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
Connect it. Get the first alert.
Connect a provider and CostMon builds a daily baseline for it. From there, a spike reaches your team as an alert.