Opportunity Name:
ML Stop Idle SageMaker Notebooks
AWS Resource Type:
SageMaker Notebook Instances
Opportunity Description:
SageMaker notebook instances that remain idle for extended periods can incur unnecessary costs. CloudFix identifies notebook instances that don't already have an idle-stop lifecycle configuration attached. When the fix is applied, CloudFix installs a lifecycle configuration that monitors Jupyter activity on the instance and automatically stops it once the configured idle period is reached, optimizing AWS SageMaker costs.
Criteria for identifying the opportunity:
- SageMaker notebook instance does not already have a lifecycle configuration attached.
- Annual cost, extrapolated from the last 31 days of usage, exceeds the annual public cost threshold (default $100).
- Once the fix is applied, the notebook is considered idle and stopped based on Jupyter activity, using a default inactivity duration of 1 hour (configurable, minimum 10 minutes).
Potential savings (range in % on annual basis):
- Stopping an idle notebook instance saves on compute costs while still incurring minimal storage costs for the underlying ML storage volume.
- For example, stopping a ml.t3.medium notebook instance, which costs around $0.066 per hour (~$48 per month), while continuing to pay for a 5GB ML storage volume at $0.50 per month.
Can CloudFix apply an automatic fix?
Yes
Other considerations:
- Data Loss: Stopping a notebook instance does not delete it or its data, minimizing the risk of data loss. Users continue to be charged for the storage of the underlying ML storage volume.
- Performance Impact: Stopping an idle notebook has no impact on active workloads. Notebooks can be easily restarted when needed.
- Security Concerns: Security configurations and data encryption remain intact for the stopped notebook instances and their associated storage volumes.
Priyanka Bhotika
Comments