Why am I unable to launch Amazon SageMaker Studio?

Last updated: 2022-11-17

I want to troubleshoot issues when I launch Amazon SageMaker Studio.

Resolution

Issues with the loading screen

You might get an error that looks similar to the following:
The loading screen is taking too long. Would you like to clear the workspace or keep waiting

You can resolve this error by doing the following:

  • Clear cache and cookies from your current browser. Sign out and sign back in to the AWS Management Console. Then, open SageMaker Studio.
  • Try using a different browser to open SageMaker Studio.

For SageMaker Studio on VPC only mode, check whether all the required endpoints are attached to subnets that are associated with your domain. For more information, see Connect SageMaker Studio notebooks in a VPC to external resources.

Issues with JupyterServer app

You might get an error that looks similar to the following:

The JupyterServer app default encountered a problem and was stopped. Restart Now

To resolve this error, try deleting all the apps from SageMaker Studio for the user by doing the following:

  1. Open the SageMaker console.
  2. In the navigation pane, choose Studio.
  3. Under Users, choose the user that's experiencing this issue.
  4. On the User Details page, choose Delete app to delete all the apps for the user.
    Be sure not to delete the actual user profile.
  5. After all the apps for the user are deleted, choose Launch app, and then choose Studio.
    SageMaker Studio reinitializes the Jupyter notebook.
    Note: You might need to wait for some time for Studio to reinitialize the notebook.

If the preceding approach doesn't work, delete the user profile by doing the following:

  1. Open the SageMaker console.
  2. In the navigation pane, choose Control panel.
  3. Under Users, choose the use that's experiencing this issue.
  4. On the User Details page, choose Delete app for all apps in the list that didn't fail.
    Be sure not to delete the actual user profile.
  5. On the Delete app dialog box, choose Yes, delete app, enter delete in the confirmation field, and then choose Delete.
  6. After the status of the apps that you deleted displays as Deleted, choose Delete user.
    Note: When a user is deleted, the user can't access the Amazon Elastic File System (Amazon EFS) volume containing data, including notebooks and other artifacts. The data isn't deleted and can be accessed by an administrator. After deleting the user, add a new user with the appropriate AWS Identity and Access Management (IAM) role. Then, try accessing SageMaker Studio with that user.

You might also get this error if the Amazon Virtual Private Cloud (Amazon VPC) where you launched Studio uses Dynamic Host Configuration Protocol (DHCP) and isn't configured correctly. If the Amazon VPC uses DHCP, then be sure that the DHCP option set is configured correctly.

  1. Open the Amazon VPC console.
  2. In the navigation pane, choose Your VPCs.
  3. Select the VPC that you want to check, and then choose Actions.
  4. Choose Edit DHCP option set.
  5. For DHCP options set, select an existing option set, and then choose Save changes.
You might get an error similar to the following:
You're attempting to set up Studio with SSO authentication in Europe (Frankfurt). Your AWS SSO is configured in Europe (Ireland). You must set up Studio in the same Region as AWS SSO or choose IAM authentication.

Currently, SageMaker doesn't support using SageMaker Studio with AWS IAM Identity Center (successor to AWS Single Sign-On) in a Region where IAM Identity Center isn't configured. The IAM Identity Center organization account must be in the same Region as SageMaker Studio. You can also onboard to Amazon SageMaker Domain using the standard setup procedure for IAM authentification.

You might get an error similar to the following:

You're attempting to set up Studio with SSO authentication in US East (N. Virginia). Your AWS SSO is configured in US East (N. Virginia). You must set up Studio in the same Region as AWS SSO or choose IAM authentication.

You might get this error even if you configured Studio and IAM Identity Center in the same Region. This error occurs if you didn't turn on IAM Identity Center in the management account or member accounts in your organization. This error is usually caused by the AccessDenied error that results when IAM Identity Center doesn't provide the sso:ListDirectoryAssociations permissions. You can resolve this issue by turning on the IAM Identity Center for the management account or member accounts.


Did this article help?


Do you need billing or technical support?