AWS bill line item
USE1-Notebk:ml.g4dn.8xlarge
Billed for every hour a classic SageMaker notebook instance sits in an active state, independent of whether anyone is actively working in it.
SageMaker notebook instance hours
Verified against official AWS documentation last checked
Why it shows up
Data scientists routinely start a notebook instance for a task and leave it running overnight, over a weekend, or indefinitely after the analysis is finished. There's no default timeout, so the meter keeps running.
Larger instance types, including GPU ones, get picked for a single heavy job and then never scaled back down for routine day-to-day notebook work.
How to cut it
- Attach an auto-stop-idle lifecycle configuration so notebooks shut down automatically after a period of inactivity.
- Schedule automatic start/stop around normal working hours.
- Move to a pay-per-app compute model instead of always-on classic notebook instances.
- Right-size the instance type to what the notebook workload needs day-to-day.
How to read this code
USE1 / USE2us-east-1 (N. Virginia) / us-east-2 (Ohio)
: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 USE1-Notebk:ml.g4dn.8xlarge 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 →Token spend moves every day.
Model prices and rate limits change between invoices. CostMon tracks your AI spend daily, so a change shows up before the bill does.