AWS sagemaker medium security documentation change
Summary
Revised end-of-support timeline and consequences, including explicit statement about discontinued security updates and user responsibility for deprecated instances.
Security assessment
Multiple changes emphasize that security updates will stop for deprecated versions and users must manage security themselves. This documents a security maintenance requirement change.
Diff
diff --git a/sagemaker/latest/dg/nbi-jl.md b/sagemaker/latest/dg/nbi-jl.md index f55b3c68a..dd26ed886 100644 --- a//sagemaker/latest/dg/nbi-jl.md +++ b//sagemaker/latest/dg/nbi-jl.md @@ -11 +11 @@ JupyterLab version maintenanceJupyterLab 4JupyterLab 3 -Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will reach end of support on June 30, 2025. We strongly recommend migrating your work to the new JupyterLab 4 notebook instances before this date to ensure you have a secure and supported environment. For more information, see JupyterLab version maintenance. +JupyterLab 1 and JupyterLab 3 are no longer supported as of June 30, 2025. You can no longer create new or restart stopped notebook instances using these versions. Existing in-service instances may continue to function but will not receive security updates or bug fixes. Migrate to JupyterLab 4 notebook instances for continued support. For more information, see JupyterLab version maintenance. @@ -34 +34 @@ You can configure your notebook to run your preferred JupyterLab version by sele -Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will reach its end of standard support on June 30, 2025. Effective on this date: +JupyterLab 1 and JupyterLab 3 platforms reached end of standard support on June 30, 2025. As of this date: @@ -36 +36 @@ Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will r - * You will no longer be able to create new, or restart stopped, JupyterLab 1 and JupyterLab 3 notebook instances. + * You can no longer create new or restart stopped JupyterLab 1 and JupyterLab 3 notebook instances. @@ -38 +38 @@ Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will r - * Existing in-service JupyterLab 1 and JupyterLab 3 notebook instances may continue to function, but will no longer receive SageMaker AI security updates or critical bug fixes. + * Existing in-service JupyterLab 1 and JupyterLab 3 notebook instances may continue to function, but no longer receive SageMaker AI security updates or critical bug fixes. @@ -40 +40 @@ Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will r - * You will be responsible for managing the security of these instances on JupyterLab 1 and JupyterLab 3. + * You are responsible for managing the security of these deprecated instances. @@ -42 +42 @@ Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will r - * If any issues arise with the existing JupyterLab 1 or JupyterLab 3 notebook instances, SageMaker AI cannot guarantee their continued availability without migrating the workload to a new JupyterLab 4 notebook instance. + * If issues arise with existing JupyterLab 1 or JupyterLab 3 notebook instances, SageMaker AI cannot guarantee their continued availability. You must migrate your workload to a JupyterLab 4 notebook instance. @@ -47 +47 @@ Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will r -We strongly recommend migrating your work to the new JupyterLab 4 notebook instances (platform identifier [notebook-al2-v3](https://docs.aws.amazon.com/sagemaker/latest/dg/nbi-al2.html#nbi-al2-instances)) before June 30, 2025 to ensure you have a secure and supported environment. This will allow you to leverage the latest versions of Jupyter notebooks, JupyterLab, and other ML libraries. For instructions, see [ migrate your work to an SageMaker AI notebook instance with Amazon Linux 2](https://aws.amazon.com/blogs/machine-learning/migrate-your-work-to-amazon-sagemaker-notebook-instance-with-amazon-linux-2/). +Migrate your work to JupyterLab 4 notebook instances (platform identifier [notebook-al2-v3](https://docs.aws.amazon.com/sagemaker/latest/dg/nbi-al2.html#nbi-al2-instances)) to ensure you have a secure and supported environment. This allows you to leverage the latest versions of Jupyter notebooks, JupyterLab, and other ML libraries. For instructions, see [ migrate your work to an SageMaker AI notebook instance with Amazon Linux 2](https://aws.amazon.com/blogs/machine-learning/migrate-your-work-to-amazon-sagemaker-notebook-instance-with-amazon-linux-2/). @@ -89 +89 @@ JupyterLab 4 has the following package version changes from JupyterLab 3: -Notebook instances running on the JupyterLab 1 and JupyterLab 3 platforms will reach end of support on June 30, 2025. We strongly recommend migrating your work to the new JupyterLab 4 notebook instances before this date to ensure you have a secure and supported environment. For more information, see JupyterLab version maintenance. +JupyterLab 1 and JupyterLab 3 are no longer supported as of June 30, 2025. You can no longer create new or restart stopped notebook instances using these versions. Existing in-service instances may continue to function but will not receive security updates or bug fixes. Migrate to JupyterLab 4 notebook instances for continued support. For more information, see JupyterLab version maintenance.