AWS sagemaker-unified-studio documentation change
Summary
Added a new 'Local IDE troubleshooting' section with a table of common issues, categories, and resolutions for the local IDE extension.
Security assessment
The change adds general troubleshooting guidance for authentication, network access, and session management issues. While it mentions security-related concepts (e.g., authentication, SSO, IAM credentials, AccessDeniedException), these are standard operational troubleshooting steps and not documentation of a specific security vulnerability, incident response, or new security feature. The change appears to be routine documentation expansion.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md b/sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md index d7fb4037a..a77930968 100644 --- a//sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md +++ b//sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md @@ -5 +5 @@ -Troubleshooting issues related to subscriptions in Amazon SageMaker Unified StudioAmazon EBS Volume Depletion with Local Notebook ExecutionDomainSAML Identity Provider Email IssueProject Creation FailureData Explorer Visibility IssueData Catalog Visibility IssueConnection to Amazon RDS MySQL in Existing VPCVisual ETL Flow Column SelectionInvalid or expired auth token when accessing an IDEJupyterLab Configure Magic Error +Troubleshooting issues related to subscriptions in Amazon SageMaker Unified StudioAmazon EBS Volume Depletion with Local Notebook ExecutionDomainSAML Identity Provider Email IssueProject Creation FailureData Explorer Visibility IssueData Catalog Visibility IssueConnection to Amazon RDS MySQL in Existing VPCVisual ETL Flow Column SelectionInvalid or expired auth token when accessing an IDEJupyterLab Configure Magic ErrorLocal IDE troubleshooting @@ -214,0 +215,19 @@ For example, if you want to change the default Spark SQL catalog name for projec +## Local IDE troubleshooting + +The following table lists common issues with the local IDE extension, along with their categories and resolutions. + +Issue | Category | Resolution +---|---|--- +Invalid domain URL format | Authentication | Verify that the URL follows the format `https://dzd-xxxxxxxxx.sagemaker.region.on.aws`. Check for copy-paste errors. +SSO authentication fails or hangs in browser | Authentication | Clear your browser cache and cookies, try an incognito or private window, or restart your IDE. +Connection expired or token issues | Authentication | If using SSO, sign out and sign back in through the AWS Toolkit extension. If using IAM credentials, update your credentials file. +"Failed to get SSO instance info" or connection timeout | Authentication | Verify that the domain URL is accessible from your network. +Timeouts connecting to the Space | Non-public internet access | Add the required URLs to your allowlist for your extension. For example, for VS Code, add the Microsoft extension marketplace URLs to your allowlist. +VPC-only domain without internet access | Non-public internet access | Configure a NAT gateway or proxy for internet access. Completely isolated domains require additional setup for remote connections. +"Failed to start SageMaker session" | Session and connection | Check the browser tab that opens for the specific error. Verify your permissions, or reduce the number of active sessions. +Remote SSH fails with "Invalid hostname format. Expected format: `sm_<creds-type>_<AWSResourceARN>`" | Session and connection | Remove previous SSH config entries from other IDEs by choosing Open SSH Configuration File in the command palette, then reinstall the extension. +Multiple browser windows open with error messages after a Space shuts down | Session and connection | In your user settings, set `remote.SSH.serverShutdownTimeout` to a lower value, such as 5. +AccessDeniedException on project node | Data Explorer | Contact your administrator to verify or grant project access. +"Failed to obtain project credentials" | Data Explorer | Re-authenticate through the extension, or update your credentials file. +"No AWS account region found in tooling environment" | Data Explorer | Verify that your project has a valid tooling environment configured. +