Migrate AWS SageMaker Notebook to JupyterLab 4

With AWS SageMaker Notebooks running JupyterLab 1 and JupyterLab 3 reaching end of standard support on 30 June 2025, AWS recommends migrating your Notebooks using Amazon Elastic Block Storage (EBS) volumes.

An alternative is to use S3 as follows:

1. Create an S3 bucket (you can also use an existing S3 bucket). The following commands assume the S3 bucket name is sm-backup.
2. Start your AWS SageMaker Notebook and open JupyterLab.
3. In the left panel, create a new folder called backup.
4. Move folders and files that you want to backup into the backup folder.
5. Open 'Terminal' and run the following commands:

zip -r SageMaker/notebook-backup.zip SageMaker/backup
aws s3 cp SageMaker/notebook-backup.zip s3://sm-backup

Create the new JupyterLab 4 Notebook, open 'Terminal' and run the following commands:

aws s3 cp s3://sm-backup/notebook-backup.zip SageMaker
unzip SageMaker/notebook-backup.zip

Move folders and files out of the backup folder and your migration is now complete.

Delete the backup folder, delete the notebook-backup.zip file, delete the old SageMaker Notebook and delete the S3 bucket (if required).