AWS bill line item
SpotUsage:m5.large
The hourly running time of an EC2 Spot Instance of the given type, billed at the fluctuating Spot market price instead of the fixed On-Demand rate.
Spot instance hours
Verified against official AWS documentation last checked
Why it shows up
Spikes when Spot capacity gets scarce and the market price rises, or when a workload scales out more Spot capacity: a batch-job burst, or an Auto Scaling group configured to prefer Spot.
Because Spot price varies by instance type, AZ, and time, the same fleet size can cost noticeably more from one week to the next with no change in usage volume.
How to cut it
- Diversify across multiple instance types/families and AZs so the fleet draws from a deeper capacity pool instead of one scarce type.
- Use a capacity-optimized allocation strategy to reduce interruption-driven relaunch churn.
- Configure a mixed-instances policy with automatic fallback to a different pool (or On-Demand) instead of retrying the same one.
How to read this code
:instanceType suffixThe specific instance type or size a charge applies to, e.g. BoxUsage:m5.large. One line per distinct type in use.
Source
Source: AWS docs →Found SpotUsage:m5.large 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 →A bill read by hand goes stale tomorrow.
Reading one export line by line takes real work. CostMon reads the next one for you, every day, for every provider you connect.