These rules identify running SageMaker notebook instances that may no longer be needed, helping avoid unnecessary compute charges.
| Rule ID | Scan Type | Name |
|---|---|---|
| CLDBRN-AWS-SAGEMAKER-1 | Discovery | SageMaker Notebook Instance Running |
CLDBRN-AWS-SAGEMAKER-1
SageMaker Notebook Instance Running
Scan type: Discovery
What it checks
Flags SageMaker notebook instances whose status remains InService. Running notebook instances incur compute charges continuously until stopped.
Why it matters
SageMaker notebook instances are billed per second while in the InService state. A ml.t3.medium notebook instance costs roughly $50/month running 24/7. Data scientists frequently leave notebook instances running after their analysis is complete, leading to persistent compute charges for idle resources.
What triggers a finding
notebookInstanceStatus is InService.
How to remediate
Stop the notebook instance when it is not actively in use. Consider implementing lifecycle configuration scripts that automatically stop idle instances after a period of inactivity. SageMaker Studio provides a more managed alternative with automatic shutdown capabilities.
aws sagemaker stop-notebook-instance --notebook-instance-name my-notebook
See Also
- CLI discover command - scan live AWS resources
- SDK Reference - run discovery programmatically