Skip to content

migrate workloads to the new SageMaker Studio [2], which supports the latest JupyterLab 4.

0

I recieved this from aws: We have identified that your AWS account runs one or more Amazon SageMaker Studio Classic notebooks on JupyterLab 3. A list of all SageMaker domains running Studio Classic notebooks on JupyterLab 3 can be found in the 'Affected Resources' tab of your AWS Health Dashboard.

We recommend that you migrate your workloads to the new SageMaker Studio [2], which supports the latest JupyterLab 4. The new SageMaker Studio offers enhanced features and capabilities compared to the Studio Classic apps [3].

Now how to migrate it, AWS Health Dashboard show Sagemaker planned lifecycle event with affected sagemaker domain, but i can't find any setting to update jupyterlab version in domain, or user profiles studio or even for created spaces and all

1 Answer
0

To migrate your workloads from Amazon SageMaker Studio Classic (which uses JupyterLab 3) to the new Amazon SageMaker Studio (which supports JupyterLab 4), you'll need to follow a migration process rather than simply updating a setting. Here's an overview of the migration steps:

  1. Enable the new Studio experience: For existing customers with accounts created before November 30, 2023, Studio Classic may be the default experience. You can enable the new Studio as your default experience using either the AWS Command Line Interface (AWS CLI) or the Amazon SageMaker AI console.

  2. Migrate the UI: This is a one-time, low-effort task. Create a test domain to ensure the new Studio is compliant with your organization's network configurations before migrating your existing domain's UI from Studio Classic to Studio.

  3. Migrate custom images and lifecycle configuration scripts (if applicable): This is an optional, medium-effort task for moving custom images and lifecycle configuration scripts from Studio Classic to the new Studio.

  4. Migrate data: This is an optional, more intensive task that involves using AWS DataSync to migrate data from the Studio Classic Amazon Elastic File System (EFS) volume to either a target Amazon EFS or Amazon Elastic Block Store (EBS) volume.

It's important to note that between July and August 2024, AWS will automatically upgrade the default landing experience for users to the new Studio experience. This change only affects the default landing UI, and the Studio Classic application will still be accessible from the new Studio UI.

Before migrating, ensure that your domain's execution role has the necessary permissions, the default landing experience is set to Studio, and if you're using an Amazon VPC, it's configured for Studio using the Studio VPC endpoint.

Remember, you won't find a simple setting to update the JupyterLab version in your domain, user profiles, or spaces. Instead, you need to follow this migration process to move from Studio Classic (JupyterLab 3) to the new Studio experience (JupyterLab 4).
Sources
Migration from Amazon SageMaker Studio Classic - Amazon SageMaker AI
Amazon SageMaker Studio - Amazon SageMaker AI

answered 2 years ago

  • but studio from my user profile shows running JupyterLab is the latest web-based IDE for notebooks, code, and data. You can select your image and instance to harness the power of AWS when running your machine learning applications. and Studio Classic is a legacy IDE that allows you to access the previous iteration of SageMaker Studio from within the new Studio experience. so is it only ui change and my instance having appliction "JupyterLab" will work fine and it is for application "Studio Classic" notebook only also i created sagemaker domain on Oct 18, 2024

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.