CODEWITHSUNDEEP
amazon-sagemakeramazon-sagemaker-studio
Ray Hogan
Ray Hogan

Reputation: 349

SageMaker Studio credentials errors

I can no longer view projects, pipelines or create new note books. The complaint appears to be credential related.

Failed to launch app [None]. Error when retrieving credentials from container-role: Error retrieving metadata: Received non 200 response (400) from ECS metadata: ResourceNotFoundException

Has anyone run into this before? Nothing should have changed in the environment.

enter image description here

Additionally, when I view my user in SageMaker console, it doesn't have an arn listed under the Execution Role section: enter image description here

Editing the user and re-saving it doesn't populate the role either. The role exists in IAM and it appears in the wizard when I edit the user details: enter image description here

Upvotes: 3

Views: 2441

Answers (2)

Warlax56
Warlax56

Reputation: 1202

Creating a more intuitive UI based solution:

  1. go to sage maker: Go to sage maker

  2. go to the affected domain: enter image description here

  3. go to the affected user profile enter image description here

  4. delete this. enter image description here

then relaunch studio as you normally would. If you deleted the right server it should say that it's creating a new one. Your files will remain.

Upvotes: 3

Ray Hogan
Ray Hogan

Reputation: 349

We resolved this issue by deleting the JupyterServer from the user profile and then re-launching Studio which will automatically create a new one (user data isn't affected as it is stored in EFS). One caveat is that we were unable to use the UI to delete the JupyterServer. The delete option was there but nothing happened when clicked, instead we had to use the CLI to remove it.

This had to be done on every user profile.

Upvotes: 2

Related Questions