Skip to main content
Scheduling · Medium severity

SageMaker Notebook Missing Auto-Stop

A notebook instance bills for its machine type until someone stops it, and a lifecycle script is the only thing that will do it unprompted.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

AWSprovider
Mediumseverity
Savingswhere it shows up
Manualfix, steps written out

AWS

Found, explained, handed over.

Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Add an auto-stop lifecycle configuration to the SageMaker notebook. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
SageMaker Notebooks on AWS
The fix, by hand
  1. SageMaker → Notebook instances → the resource → confirm currently running.
  2. SageMaker → Lifecycle configurations → Create configuration → name it auto-stop-idle.
  3. Paste an on-start hook that runs an idle-watcher script (AWS publishes a reference cron-based auto-stop script in the SageMaker examples GitHub).
  4. Set idle timeout: 1h for dev, 4h for shared notebooks.
  5. SageMaker → Notebook instances → the resource → Stop → Edit → attach the lifecycle config → Start.
  6. Long-term: migrate to SageMaker Studio (built-in idle shutdown, no script required).

These are the steps the finding carries in the product.

Category
Scheduling. Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.
Where it appears
The Savings tab of Recommendations, with every affected resource listed.
Rule ID
RC-1502
Full reference

SageMaker Notebook Missing Auto-Stop

Related checks

SageMaker Notebook Direct Internet Access EnabledAWSSageMaker Notebook Volume Not Encrypted with CMKAWSSageMaker Notebook Not in a VPCAWSSageMaker Notebook Root Access EnabledAWSSageMaker Notebook Has No Lifecycle ConfigurationAWSIdle SageMaker HyperPod Cluster, Near-Zero UtilisationAWS

See the always-on resources in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·