AWS bill line item
BoxUsage:m5.large
The hourly running time of an On-Demand EC2 instance of the given type, in the given region. This is the base compute rate before other EC2 charges (storage, data transfer) are added.
On-Demand instance hours
Verified against official AWS documentation last checked
Why it shows up
This is usually the largest line on an EC2-heavy bill: every running On-Demand instance generates one BoxUsage row per instance type per region, per hour. A spike usually means more instances, larger instance types, or instances left running (forgotten dev/test boxes, autoscaling that scaled up and never fully scaled back down).
It also appears for managed services that run on EC2 under the hood, so a fleet-size change in a managed service can show up here too.
How to cut it
- Buy Savings Plans or Reserved Instances for steady-state baseline usage. The BoxUsage line stays, but the effective rate drops.
- Right-size instance types using utilization recommendations rather than guessing.
- Schedule or auto-stop non-production instances outside business hours.
- Audit for orphaned instances: stopped-but-not-terminated, or running with no real traffic.
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 BoxUsage: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.