JupyterLab versioning - Amazon SageMaker AI
JupyterLab 4JupyterLab 3

JupyterLab versioning

Important

Custom IAM policies that allow Amazon SageMaker Studio or Amazon SageMaker Studio Classic to create Amazon SageMaker resources must also grant permissions to add tags to those resources. The permission to add tags to resources is required because Studio and Studio Classic automatically tag any resources they create. If an IAM policy allows Studio and Studio Classic to create resources but does not allow tagging, "AccessDenied" errors can occur when trying to create resources. For more information, see Provide permissions for tagging SageMaker AI resources.

AWS managed policies for Amazon SageMaker AI that give permissions to create SageMaker resources already include permissions to add tags while creating those resources.

The Amazon SageMaker notebook instance interface is based on JupyterLab, which is a web-based interactive development environment for notebooks, code, and data. Notebooks now support using either JupyterLab 1, JupyterLab 3, or JupyterLab 4. A single notebook instance can run a single instance of JupyterLab (at most). You can have multiple notebook instances with different JupyterLab versions.

You can configure your notebook to run your preferred JupyterLab version by selecting the appropriate platform identifier. Use either the AWS CLI or the SageMaker AI console when creating your notebook instance. For more information about platform identifiers, see Amazon Linux 2 vs Amazon Linux notebook instances. If you don’t explicitly configure a platform identifier, your notebook instance defaults to running JupyterLab 1.

Topics

JupyterLab 4

JupyterLab 4 support is available only on the Amazon Linux 2 operating system platform. JupyterLab 4 includes the following features that are not available in JupyterLab 3:

  • Optimized rendering for a faster experience

  • Opt-in settings for faster tab switching and better performance with long notebooks. For more information, see the blog post JupyterLab 4.0 is Here.

  • Upgraded text editor

  • New extension manager installing from pypi

  • Added improvements to the UI, including document search and accessibility improvements

You can run JupyterLab 4 by specifying notebook-al2-v3 as the platform identifier when creating your notebook instance.

Note

If you attempt to migrate to a JupyterLab 4 Notebook Instance from another JupyterLab version, the package version changes between JupyterLab 3 and JupyterLab 4 might break any existing lifecycle configurations or Jupyter/JupyterLab extensions.

Package version changes

JupyterLab 4 has the following package version changes from JupyterLab 3:

  • JupyterLab has been upgraded from 3.x to 4.x.

  • Jupyter notebook has been upgraded from 6.x to 7.x.

  • jupyterlab-git has been updated to version 0.50.0.

JupyterLab 3

JupyterLab 3 support is available only on the Amazon Linux 2 operating system platform. JupyterLab 3 includes the following features that are not available in JupyterLab 1. For more information about these features, see JupyterLab 3.0 is released!.

  • Visual debugger when using the following kernels:

    • conda_pytorch_p38

    • conda_tensorflow2_p38

    • conda_amazonei_pytorch_latest_p37

  • File browser filter

  • Table of Contents (TOC)

  • Multi-language support

  • Simple mode

  • Single interface mode

  • Live editing SVG files with updated rendering

  • User interface for notebook cell tags

Important changes to JupyterLab 3

For information about important changes when using JupyterLab 3, see the following JupyterLab change logs:

Package version changes

JupyterLab 3 has the following package version changes from JupyterLab 1:

  • JupyterLab has been upgraded from 1.x to 3.x.

  • Jupyter notebook has been upgraded from 5.x to 6.x.

  • jupyterlab-git has been updated to version 0.37.1.

  • nbserverproxy 0.x (0.3.2) has been replaced with jupyter-server-proxy 3.x (3.2.1).