Skip to content

Unable to Start Notebook Instance - Platform identifier (notebook-al1-v1) is not supported for this service

0

I recently received a notification about scheduled maintenance that affected my notebook-al1-v1 instance. The maintenance required me to stop and start the affected Notebook instance. However, when I attempted to restart it, I encountered a ValidationException stating that the "Platform identifier (notebook-al1-v1) is not supported for this service".

Upon researching, I found that (apparently) Amazon Linux 1 is no longer supported, and the recommendation is to migrate to an Amazon Linux 2 instance. The migration process is described in this post: https://aws.amazon.com/es/blogs/machine-learning/migrate-your-work-to-amazon-sagemaker-notebook-instance-with-amazon-linux-2/

Unfortunately, the migration process requires setting up a lifecycle configuration, which isn’t working. I assume this is because the ValidationException occurs before the lifecycle script runs.

I also tried accessing the EBS volumes to connect a different notebook, but it appears that the SageMaker volumes are hidden and/or inaccessible from the console.

Is there any way to recover the notebooks I created? I appreciate any help you can provide.

  • I have the same problem. Did you find a solution?

asked 2 years ago1.9K views
1 Answer
1
Accepted Answer

Hello,

Thank you for using SageMaker.

I completely understand the blocker and the inconvenience caused due this.

To overcome this issue, I'd request you to reach out to AWS Premium Support and request them to allow your account for grace period for using ali v1 platform and once done user with "Platform identifier (notebook-al1-v1) will get grace period to migrate without any issue so that the data loss is avoid. Please note grace period is until end of June 2024.

Open a support case with AWS using the link: https://console.aws.amazon.com/support/home?#/case/create

AWS
SUPPORT ENGINEER
answered a year ago
EXPERT
reviewed 9 months ago
  • Thank you, Kartik! I had to upgrade to a Developer support plan to open the case, but it was money well spent. It took a couple of days, but we got the grace period and prevented data loss.

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.