Troubleshooting
Important
As of November 30, 2023, the previous Amazon SageMaker Studio experience is now named Amazon SageMaker Studio Classic. The following section is specific to using the updated Studio experience. For information about using the Studio Classic application, see Amazon SageMaker Studio Classic.
Important
Custom IAM policies that allow Amazon SageMaker Studio or Amazon SageMaker Studio Classic to create Amazon SageMaker resources must also grant permissions to add tags to those resources. The permission to add tags to resources is required because Studio and Studio Classic automatically tag any resources they create. If an IAM policy allows Studio and Studio Classic to create resources but does not allow tagging, "AccessDenied" errors can occur when trying to create resources. For more information, see Provide Permissions for Tagging SageMaker Resources.
Amazon Managed Policies for Amazon SageMaker that give permissions to create SageMaker resources already include permissions to add tags while creating those resources.
This section shows how to troubleshoot common problems in Amazon SageMaker Studio.
Cannot delete Code Editor, based on Code-OSS, Visual Studio Code - Open Source or JupyterLab application
This issue occurs when a user creates an application from Amazon SageMaker Studio that is only available in Studio, then reverts to the Studio Classic experience as their default. As a result, the user cannot delete an application for Code Editor, based on Code-OSS, Visual Studio Code - Open Source or JupyterLab because they can't access the Studio UI.
To resolve this issue, notify your administrator so that they can delete the application manually using the Amazon Command Line Interface (Amazon CLI).