AWS sagemaker documentation change
Summary
Added detailed Recovery mode documentation for troubleshooting configuration issues, updated application deletion guidance, and expanded quota error resolution steps. Restructured sections with proper headers and CLI examples.
Security assessment
Changes focus on operational troubleshooting (configuration recovery, quota management, application deletion) without mentioning security vulnerabilities, patches, or exploits. Recovery mode addresses system configuration issues rather than security controls.
Diff
diff --git a/sagemaker/latest/dg/studio-updated-troubleshooting.md b/sagemaker/latest/dg/studio-updated-troubleshooting.md index ac9f755c1..cfe390821 100644 --- a/sagemaker/latest/dg/studio-updated-troubleshooting.md +++ b/sagemaker/latest/dg/studio-updated-troubleshooting.md @@ -4,0 +5,2 @@ +Recovery modeCannot delete the Code Editor or JupyterLab applicationEC2InsufficientCapacityErrorInsufficient limit (quota increase required) + @@ -19 +21,70 @@ This section shows how to troubleshoot common problems in Amazon SageMaker Studi -**Cannot delete Code Editor, based on Code-OSS, Visual Studio Code - Open Source or JupyterLab application** +## Recovery mode + +Recovery mode allows you to access your Studio application when a configuration issue prevents your normal start up. It provides a simplified environment with essential functionality to help you diagnose and fix the issue. + +When an application fails to launch, you may see an error message about accessing recovery mode to address one of the following configuration issues. + + * Corrupted [`.condarc`](https://docs.conda.io/projects/conda/en/latest/user-guide/configuration/use-condarc.html) file. + +For information on troubleshooting your `.condarc` file, see the [troubleshooting](https://docs.conda.io/projects/conda/en/latest/user-guide/troubleshooting.html) page in the _Conda user guide_. + + * Insufficient storage volume available. + +You can increase the Amazon EBS space storage available for the application or enter recovery mode to remove unnecessary data. + +For information on increasing the Amazon EBS volume size, see [request a quota size](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas Developer Guide_. + + + + +In recovery mode: + + * Your home directory will differ from your normal start up. This directory is temporary and ensures that any corrupted configurations in your standard home directory does not impact your recovery mode operations. You can navigate to your standard home directory by using the command `cd /home/sagemaker-user`. + + * Standard mode: `/home/sagemaker-user` + + * Recovery mode: `/tmp/sagemaker-recovery-mode-home` + + * The conda environment uses a minimal base conda environment with essential packages only. The simplified conda setup helps isolate environment-related issues and provides basic functionality for troubleshooting. + + + + +You can use the Studio UI or the AWS CLI to access the application in recovery mode. + +The following provides instructions on accessing your application in recovery mode. + + 1. If you have not already done so, launch the Studio UI by following the instructions in [Launch from the Amazon SageMaker AI console](./studio-updated-launch.html#studio-updated-launch-console). + + 2. In the left navigation menu, under **Applications** , choose the application. + + 3. Choose the space you are having configuration issues with. + +The following steps become available to you when you have one one or more of the configuration issues mentioned previously. In this case, you will see a warning banner and **Recovery mode** message. + +###### Note + +The warning banner should have a recommended solution for the issue. Take note of it before proceeding. + + 4. Choose **Run space (Recovery mode)**. + + 5. To access your application in recovery mode, choose **Open`application` (Recovery mode)**. + + + + +To access your application in recovery mode, you must append `--recovery-mode` to your [create-app](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/create-app.html) AWS CLI command. The following provides an example on how to access your application in recovery mode. + +For the following example, you will need your: + + * `domain-id` + +To obtain your domain details, see [View domains](./domain-view.html). + + * `space-name` + +To obtain the space names associated with your domain, see [Use the AWS CLI to view the SageMaker AI spaces in your domain](./sm-console-domain-resources-view.html#sm-console-domain-resources-view-spaces-cli). + + * `app-name` + +The name of your application. To view your applications, see [Use the AWS CLI to view the SageMaker AI applications in your domain](./sm-console-domain-resources-view.html#sm-console-domain-resources-view-apps-cli). @@ -21 +92,28 @@ This section shows how to troubleshoot common problems in Amazon SageMaker Studi -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. + + + +Access Code Editor application in recovery mode + + + + aws sagemaker create-app \ + --app-name app-name \ + --app-type CodeEditor \ + --domain-id domain-id \ + --space-name space-name \ + --recovery-mode + +Access JupyterLab application in recovery mode + + + + aws sagemaker create-app \ + --app-name app-name \ + --app-type JupyterLab \ + --domain-id domain-id \ + --space-name space-name \ + --recovery-mode + +## Cannot delete the Code Editor or JupyterLab application + +This issue occurs when a user creates an application from Amazon SageMaker Studio, that is only available in Studio, then reverts their default experience to Studio Classic. 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. @@ -25 +123 @@ To resolve this issue, notify your administrator so that they can delete the app -**EC2InsufficientCapacityError** +## EC2InsufficientCapacityError @@ -56 +154 @@ P5 | 3rd Gen AMD EPYC processors | 192 | 2000 | NVIDIA H100 Tensor Core | 8 | 64 -**Insufficient limit (quota increase required)** +## Insufficient limit (quota increase required) @@ -58 +156 @@ P5 | 3rd Gen AMD EPYC processors | 192 | 2000 | NVIDIA H100 Tensor Core | 8 | 64 -This issue occurs when you get the following error when running a space. This error means that you have reached the limit on the number of instances of that type that you can launch in a Region. When you create your AWS account, we set default limits on the number of instances you can run in each Region. +This issue occurs when you get the following error message while attempting to run a space. @@ -63 +161,3 @@ This issue occurs when you get the following error when running a space. This er -To resolve this issue, request an instance limit increase for the Region that you are launching the space is. For more information, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html). +There is a default limit on the number of instances, for each instance type, that you can run in each AWS Region. This error means that you have reached that limit. + +To resolve this issue, request an instance limit increase for the AWS Region that you are launching the space in. For more information, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html).