AWS sagemaker-unified-studio documentation change
Summary
Updated prerequisites for remote IDE connections to SageMaker Unified Studio, adding Cursor IDE support and reorganizing requirements.
Security assessment
This change updates general documentation about supported IDEs, system requirements, and instance types for remote development. No security-related changes are present.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/prerequisites.md b/sagemaker-unified-studio/latest/userguide/prerequisites.md index 951f87ef1..65a292889 100644 --- a//sagemaker-unified-studio/latest/userguide/prerequisites.md +++ b//sagemaker-unified-studio/latest/userguide/prerequisites.md @@ -7 +7 @@ -Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, ensure you have the following prerequisites: +Before connecting VS Code, Kiro, or Cursor remotely to a SageMaker Unified Studio Space, ensure that you have the following prerequisites: @@ -11 +11 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * AWS Toolkit version 3.97 or higher. You can install it using either of the steps below based on your IDE: + * A supported IDE and AWS Toolkit version, as listed in the following table. @@ -13 +13,5 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * Open VS Code, navigate to Extensions and search for **AWS Toolkit**. Choose **Install** to install the latest version of the official AWS Toolkit extension. The AWS Toolkit extension will appear on the VS Code sidebar. +IDE | Minimum version | Minimum AWS Toolkit version +---|---|--- +VS Code | 1.90 or later | 3.97 or later +Kiro | 0.8.0 or later | 3.97 or later +Cursor | 2.6.18 or later | 3.100 or later @@ -15 +19 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * In Kiro, choose **Extensions** and then choose AWS toolkit. After installation, the AWS Toolkit extension appears on the sidebar. + * The AWS Toolkit extension installed from the Extensions marketplace in your IDE. @@ -17 +21 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * System Requirements + * One of the following supported operating systems: @@ -19 +23 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * **VS Code Version** : v1.90 or later (latest stable version recommended) + * macOS 13 or later @@ -21 +25 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * **Kiro Version** : 0.8.0 or later (latest stable version recommended) + * Windows 10 or Windows 11 @@ -23 +27 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * Operating Systems + * Linux (requires the official Microsoft VS Code distribution for VS Code and Cursor) @@ -25 +29 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * macOS 13+ + * A Space instance that meets the following requirements: @@ -27 +31 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * Windows 10/11 + * Memory: Minimum 8 GB RAM. We recommend instances with 8 GB or more memory for optimal performance. @@ -29 +33 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * Linux (official Microsoft VS Code distribution required) + * Unsupported instance types: `ml.t3.medium`, `ml.c7i.large`, `ml.c6i.large`, `ml.c6id.large`, `ml.c5.large` @@ -31 +35 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * Space Instance Requirements + * A compatible image: @@ -33 +37 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * **Memory** : Minimum 8GB RAM + * SageMaker Distribution: Version 2.8 or later @@ -35 +39 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * **Unsupported Instance Types** : ml.t3.medium, ml.c7i.large, ml.c6i.large, ml.c6id.large, ml.c5.large + * Custom images: Must follow SageMaker custom image specifications @@ -37,9 +41 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, - * **Recommended** : Use instances with 8GB+ memory for optimal performance - - * Image Compatibility - - * **SageMaker Distribution** : Version 2.8 or later - - * **Custom Images** : Must follow SageMaker custom image specifications - - * **Extension Compatibility** : Not all VS Code extensions support remote development + * Extension compatibility: Not all VS Code extensions support remote development. @@ -52 +48 @@ Before connecting VS Code or Kiro remotely to a SageMaker Unified Studio Space, -Remote Space connections are currently not supported for TIP (Trusted Identity Propagation) enabled Projects. For instructions on how to set the `enableTrustedIdentityPropagationPermissions` to false to use remote connection for Spaces, see [Trusted identity propagation](https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/trusted-identity-propagation.html). +Remote Space connections are not supported for TIP (Trusted Identity Propagation) enabled projects. For instructions on how to set the `enableTrustedIdentityPropagationPermissions` parameter to false to use remote connection for Spaces, see [Trusted identity propagation](https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/trusted-identity-propagation.html).