Why am I unable to launch Amazon SageMaker Studio?

Resolution

Loading screen issues

If the loading screen stops responding, then you see the following message:

The loading screen is taking too long. Would you like to clear the workspace or keep waiting

To resolve the error, take the following steps:

1. Clear cache and cookies from your current browser.
2. Sign out and sign back in to the AWS Management Console.
3. Open SageMaker Studio.

If you still receive loading screen errors, then use 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 Requirements to use VPC only mode.

JupyterServer app issues

If the JupyterServer app encounters a problem, then you see the following message:

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

To resolve this error, delete all apps from SageMaker Studio for the user:

1. Open the SageMaker console.
2. On the left navigation pane, choose Admin configurations.
3. Under Admin configurations, choose domains.
4. Select the domain that you must delete.

Repeat the following steps for each user in the User profiles list.

1. Choose the user.
2. On the User Details page, for each non-failed app in the Apps list, choose Action.
3. From the dropdown list, choose Delete.
4. On the Delete app dialog box, choose Yes, delete app. Then enter delete in the confirmation field, and choose Delete.
5. After all the apps for the user are deleted, choose Launch app, and then choose Studio.
   SageMaker Studio will reinitialize the Jupyter notebook.

If the preceding approach doesn't work, then remove user profiles and recreate the profiles.

Note: If a user is deleted, then the user can't access the Amazon Elastic File System (Amazon EFS) volume. The volume data isn't deleted and an administrator can access it.

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 again.

Error with Amazon Virtual Private Cloud (Amazon VPC)
You might also get this error if the Amazon VPC where you launched SageMaker Studio uses Dynamic Host Configuration Protocol (DHCP) and isn't configured correctly. If the Amazon VPC uses DHCP, then verify 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 you want to check, and then choose Actions.
4. Choose Edit DHCP option set.
5. For DHCP options set, select any existing option set, and then choose Save changes.

IAM Identity Center issues

If there is a SageMaker Studio and IAM Identity Center region mismatch, then you see the following error:

"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."

The IAM Identity Center must be set up in the same Region as SageMaker Studio. Or, you can onboard to Amazon SageMaker Domain using the standard setup procedure for IAM authentification.

Issues related to Region

If the SageMaker Studio and IAM Identity Center are in the same Region, you still might see the following error:

"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."

This error occurs if IAM Identity Center isn't activated 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. Resolve this issue by turning on the IAM Identity Center for the management account or member accounts.