A SageMaker notebook instance has been running for several weeks and new Jupyter and SageMaker software updates are available. Your security policy requires that running notebook instances use the latest SageMaker-managed software and security updates. What is the simplest way for a data scientist to ensure the notebook instance receives those updates?

Stopping and restarting a SageMaker notebook instance is the simplest way to apply SageMaker-managed software and security updates. When an instance is stopped and then started, SageMaker automatically provisions a new underlying EC2 instance with the latest updates for the chosen instance type and image. Creating a brand-new instance and attaching the EBS volume is overly complex and unnecessary, as a simple stop/start achieves the same update. Lifecycle configurations (CreateNotebookInstanceLifecycleConfig or UpdateNotebookInstanceLifecycleConfig) are used for custom scripts that run during instance creation or start-up, not for applying SageMaker's core software updates.