- Newest
- Most votes
- Most comments
Yes, you can stop your SageMaker notebook instance after creating a scheduled notebook job on it. The jobs will run independently from the notebook instance.
When you create a scheduled notebook job, it will use the IAM role and permissions configured for the notebook instance. So the job will have access to the same S3 buckets and be able to call SageMaker APIs.
The job definition specifies the notebook path and schedule. It does not depend on the original notebook instance remaining running. The jobs will execute based on the schedule using the resources defined in the IAM role.
It is generally not required to keep the original notebook instance running after creating scheduled jobs. You can stop the instance to avoid ongoing compute costs. The jobs will still run as scheduled.
For best practices, consider using SageMaker Pipelines for more advanced workflows that chain multiple jobs together based on dependencies. You can define pipelines that run Job A, then Job B, etc.
Relevant content
- asked a month ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago