SageMaker notebook instances are billed continuously while in an active state — and critically, they do not automatically shut down when idle. Closing a browser tab, shutting down a Jupyter kernel, or simply walking away does not stop the underlying compute instance. This creates a pervasive waste pattern in ML and data science teams: a developer spins up a powerful GPU instance for experimentation, finishes their work, closes the browser, and assumes the resource is no longer running. In reality, the instance continues accruing per-second charges around the clock until it is explicitly stopped.

This is particularly costly because ML workloads often require high-performance instance types with GPUs. A single forgotten GPU notebook instance can generate thousands of dollars in monthly charges with zero productive use. The problem is compounded in team environments where multiple data scientists each maintain their own notebook instances, and there is no organizational process for reviewing or reclaiming idle resources. The classic scenario — an instance left running over a weekend or holiday — is one of the most common and avoidable sources of ML infrastructure waste.

Unlike SageMaker Studio, which offers native automatic shutdown of idle applications, traditional notebook instances have no built-in idle detection or auto-stop capability. Without explicit lifecycle configuration scripts or external automation, these instances will run indefinitely. The user experience itself is deceptive: the act of closing a notebook feels like shutting down, but the billable compute continues silently in the background.