Sagemaker Studio Notebook: Failed to start kernel and Error listing projects. Error message: undefined. Args: "Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1"

0

I have an issue with Sagemaker Studio: I can not see my projects, pipelines, nor work with Notebooks. So, I have been working with Sagemaker for more than 1 year, and never faced an issue like this before. Three days ago, everything worked as it should, I executed many pipelines, worked on my notebook, and now nothing works. When I open Sagemaker Studio, and when I click on Sagemaker Resources->Projects, the following error is displayed: Error for Projects Also, If I want to see my pipelines, this is the error that is displayed: Error for pipelines And if I want to work on some of my notebooks there, here is the error that I got for any kernel that I choose (the ones that are provided from AWS): Error for starting a kernel I never used local mode, I just worked on AWS Sagemaker Studio Project and that's it. My account has Access Key and Access Secret and it is activated. What can be an issue? Is it something related to a config file? If yes, where can I find that AWS_CONFIG_FILE? (Note: Also, I have never used AWS CLI, because I never needed it, is this an issue that can be fixed only through AWS CLI?)

2 Answers
1
Accepted Answer

It appears that the error is potentially related to the JupyterLab version that you are using in SageMaker Studio. It's possible that the version of JupyterLab you're using is now outdated. [1]

Could you please confirm which JupyterLab version your studio app is currently using? Please refer to this on how to view the version [2]

To fix the problem, I recommend that you update your JupyterLab to the latest version. Please refer to this documentation for futher details. [2]

References:

[1]https://docs.aws.amazon.com/sagemaker/latest/dg/studio-jl.html

[2]https://docs.aws.amazon.com/sagemaker/latest/dg/studio-jl.html#studio-jl-view

AWS
answered 10 months ago
  • Yes, the issue is related to the version of JupyterLab. I fixed it. Thank you for helping me out.

1

Hi, have a look at this response: https://github.com/aws/aws-sdk-js/issues/3665#issuecomment-1272257650 Folks seem to have an issue similar to yours coming from upgrades and one found a solution. Hope it works for you as well! Didier

profile pictureAWS
EXPERT
answered 10 months ago

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.

Guidelines for Answering Questions