Why can't I launch Amazon SageMaker Studio?

Resolution

To identify the issue that causes your SageMaker Studio launch to fail, use Amazon CloudWatch Logs to review your applications for errors. To review CloudWatch logs, complete the following steps:

1. Open the CloudWatch console.
2. In the navigation pane, under Logs, choose Log Groups.
3. On the Log Groups page, search for /aws/sagemaker/studio.
4. In the log streams that appear, select the log stream for the application that fails to launch.
5. Filter the log stream for the timeframe of your launch failure.
6. Review the logs that have errors or exception messages.

If your SageMaker Studio fails to launch because of a network configuration issue, then generate a HAR file to review the HTTP error code.

Complete the resolution for your issue.

Lifecycle configuration script errors

If you attach incorrect lifecycle configurations to the domain level of your SageMaker Studio or user profile, then the application can fail to launch.

To troubleshoot lifecycle configuration script issues, complete the following steps:

1. Open CloudWatch console.
2. In the navigation pane, under Logs, choose Log Groups.
3. In the search bar, enter /aws/sagemaker/studio, and then select the result.
4. In the log streams that appear, choose [domain-id]/[user-profile-name]/[app-type]/[app-name]/LifecycleConfigOnStart.
5. Filter the log stream for the timeframe of your launch failure.
6. After you identify the error, detach your existing lifecycle script.
7. Create and attach a new lifecycle script.

Loading screen error

If the loading screen doesn't respond, then you receive the following message:

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

To resolve this error, complete the following steps:

1. Clear the cache and cookies in your current browser.
2. Sign out of the AWS Management Console, and then sign in again.
3. Open your SageMaker Studio application.

If you still receive a loading screen error message, then use a different browser to open SageMaker Studio.

For SageMaker Studio on VPC only mode, make sure that you attach the required endpoints to your domain's associated subnets. For more information, see Requirements to use VPC only mode.

If the SageMaker Studio launcher doesn't appear, then reset your workspace. Go to the URL that you see when you try to launch SageMaker Studio. At the end of the URL, if ?=reset is missing, add it, and then press Enter.

JupyterServer app errors

If the JupyterServer app encounters a problem, then you receive 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.

Complete the following steps:

1. Open the SageMaker AI console.
2. In the navigation pane, choose Admin configurations, and then choose Domains.
3. Select your domain.
4. Under User profiles, select a user.
5. On the User Details page, for each non-failed app in the Apps list, choose Action.
6. From the dropdown list, choose Delete.
7. On the Delete app dialog box, choose Yes, delete app. In the confirmation field, enter delete, and then choose Delete.
8. After you delete all the apps for the user, choose Launch app, and then choose Studio.
9. Repeat steps 4-8 for each user under User profiles.

SageMaker Studio restarts the Jupyter notebook. If the issue doesn't resolve, then remove the user profiles and recreate the profiles.

Note: If you delete a user, then that user can't access the Amazon Elastic File System (Amazon EFS) volume. However, an administrator can still access the volume data.

After you delete the user, add a new user with the appropriate AWS Identity and Access Management (IAM) role. Then, try to access SageMaker Studio with that user.

When you launch JupyterServer applications, you might receive the "ERR_EMPTY_RESPONSE" error. If you use a Google Chrome browser to access a website and data isn't transmitting, then you might receive this error.

To resolve the "ERR_EMPTY_RESPONSE" error, take one or more of the following actions:

• Check that your network is operational and stable.
• Clear your browser's cookies.
• Use a different browser.
• Recreate the applications.

Amazon VPC error

If the Amazon Virtual Private Cloud (Amazon VPC) where you launch SageMaker Studio uses Dynamic Host Configuration Protocol (DHCP), then you might receive the following error:

"The JupyterServer app default encountered a problem and was stopped. If you continue to experience issues, please contact Customer Service.Details: InternalFailure"

To verify that you correctly configured the DHCP option set, complete the following steps:

1. Open the Amazon VPC console.
2. In the navigation pane, choose Your VPCs.
3. Select your VPC, and then choose Actions.
4. Choose Edit DHCP option set.
5. For DHCP options set, choose any existing option set, and then choose Save changes.

IAM Identity Center error

If your SageMaker Studio isn't in the same AWS Region as AWS IAM Identity Center, then you receive 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. To onboard your SageMaker AI domain, use the custom setup process for IAM authentication.

Note: Make sure to activate IAM Identity Center for your AWS Organizations management account or member accounts.

AWS CloudTrail Event History

If there are permissions issues related to the API calls that you use to launch SageMaker Studio, then the launch fails.

To identify whether there are permissions issues, complete the following steps:

1. Open AWS CloudTrail console.
2. In the navigation pane, choose Event History.
3. Choose Lookup Attributes, and then from the dropdown list choose Event Source.
4. Select sagemaker.amazonaws.com.
5. After the events load, look for failed CreateApp events that occurred when you tried to launch SageMaker Studio, and then choose the event.
6. Review the error messages to identify missing permissions. For example, you might see an error message similar to "PermissionError : User "XYZ" is not authorized to perform sagemaker:CreateApp on this resource resource_ARN".
7. Add the required permissions to your user identity, and then launch Studio SageMaker.