How SageMaker Actually Bills: A Breakdown for Engineers

You deployed a SageMaker notebook to prototype a model. A week later, your AWS bill has a $280 line item you can't explain. Sound familiar? SageMaker is one of the most powerful ML platforms on AWS — and one of the most confusing to bill for. Unlike EC2 (one instance, one hourly rate), SageMaker has at least 12 independent billing dimensions spread across notebooks, training, endpoints, storage, data processing, and more. Each one ticks on its own meter. This post breaks down every SageMaker billing component, shows you the real numbers, and highlights the traps that catch even experienced AWS engineers. The Core Mental Model: SageMaker Is Not One Service Think of SageMaker as a collection of services that share a console. Each has its own pricing: ┌─────────────────────────────────────────────────┐ │ SageMaker │ │ │ │ ┌──────────┐ ┌──────────┐ ┌───────────────┐ │ │ │ Notebooks│ │ Training │ │ Endpoints │ │ │ │ (Dev) │ │ (Build) │ │ (Serve) │ │ │ │ $/hr │ │ $/hr │ │ $/hr 24/7 │ │ │ └──