Amazon SageMaker Notebook instance now supports self-service migration, allowing you to update your notebook instance platform identifier through the UpdateNotebookInstance API. This enables you to seamlessly transition from unsupported platform identifiers (notebook-al1-v1, notebook-al2-v1, notebook-al2-v2) to supported versions (notebook-al2-v3, notebook-al2023-v1).
With the new PlatformIdentifier parameter in the UpdateNotebookInstance API, you can update to newer versions of the Notebook instance platform while preserving your existing data and configurations. The platform identifier determines which Operating System and JupyterLab version combination your notebook instance runs. This self-service capability simplifies the migration process and helps you keep your notebook instances current.
This feature is supported through AWS CLI (version 2.31.27 or newer) and SDK, and is available in all AWS Regions where Amazon SageMaker Notebook instances are supported. To learn more, see Update a Notebook Instance in the Amazon SageMaker Developer Guide.
Categories: general:products/aws-govcloud-us,general:products/amazon-sagemaker-studio,general:products
Source: Amazon Web Services
Latest Posts
- Amazon SageMaker now supports self-service migration of Notebook instances to latest platform versions

- Amazon SES adds VPC support for API endpoints

- TwelveLabs’ Pegasus 1.2 model now in 23 new AWS regions via Global cross-region inference

- (Updated) Microsoft Viva: Transition to VFAM-based exclusion management [MC1188597]
![(Updated) Microsoft Viva: Transition to VFAM-based exclusion management [MC1188597] 5 pexels ivan drazic 20457695 13370450](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)




![(Updated) Microsoft Viva: Transition to VFAM-based exclusion management [MC1188597] 5 pexels ivan drazic 20457695 13370450](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-ivan-drazic-20457695-13370450-150x150.webp)