SageMaker notebook instances should run on supported platforms

How to fix it

• Interrupts service: The instance must be stopped for the update, and a stopped AL2 instance cannot start again until the update to notebook-al2023-v1 succeeds.
• Can break clients: AL2023 installs packages with dnf instead of yum, so change yum commands in the lifecycle configuration script before starting the instance.

In the console

SageMaker AI → Notebook instances → the stopped instance → Edit → Platform identifier

Platform identifier

notebook-al2023-v1; an AL1 instance (notebook-al1-v1) is not migrated in place and needs a new instance instead

Notebook instance type

Change ml.p2, ml.p3, ml.p3dn, ml.inf1 or ml.g3 in the same update; AL2023 does not support them

With the AWS CLI

aws sagemaker update-notebook-instance --notebook-instance-name <notebook-instance-name> --platform-identifier notebook-al2023-v1 --region <region>

With Terraform

• Replaces the resource: platform_identifier forces a new instance, so an apply destroys this one and its volume: update through the console or CLI, then set platform_identifier to match.

resource "aws_sagemaker_notebook_instance" "this" {
  name                = var.notebook_instance_name
  instance_type       = var.instance_type
  role_arn            = var.execution_role_arn
  platform_identifier = "notebook-al2023-v1"
}