AWS sagemaker documentation change
Summary
Restructured documentation, added SSH CLI connection steps with Session Manager, and clarified setup requirements
Security assessment
Added SSH CLI connection instructions using AWS Session Manager, which is a security best practice for secure access. However, this documents existing security features rather than addressing a specific vulnerability.
Diff
diff --git a/sagemaker/latest/dg/remote-access-local-ide-setup.md b/sagemaker/latest/dg/remote-access-local-ide-setup.md index 4bb962f7a..405d3131f 100644 --- a//sagemaker/latest/dg/remote-access-local-ide-setup.md +++ b//sagemaker/latest/dg/remote-access-local-ide-setup.md @@ -5 +5 @@ -Enable remote access for your spaceSet up your local environmentConnect to your local VS Code +Set up your local environmentConnect to your local VS Code @@ -11,9 +11 @@ After administrators complete the instructions in [Connect your local Visual Stu -## Enable remote access for your space - -###### Note - -This setup only needs to be done once. - -### For an existing space - -Activate remote access for your SageMaker space: +###### Topics @@ -21 +13 @@ Activate remote access for your SageMaker space: - 1. Open the SageMaker AI UI. + * Set up your local environment @@ -23 +15 @@ Activate remote access for your SageMaker space: - 2. Navigate to your space. + * Connect to your local VS Code @@ -25 +17 @@ Activate remote access for your SageMaker space: - 3. In the space details, toggle on **Remote Access**. + * [Connect to VPC with subnets without internet access](./remote-access-local-ide-setup-vpc-no-internet.html) @@ -27 +19 @@ Activate remote access for your SageMaker space: - 4. Start your space. + * [Filter your Studio spaces](./remote-access-local-ide-setup-filter.html) @@ -39,0 +32,11 @@ Before you can establish a connection from your local Visual Studio Code to your +###### Topics + + * Method 1: Deep link from Studio UI + + * Method 2: AWS Toolkit for Visual Studio Code + + * Method 3: Connect from the terminal via SSH CLI + + + + @@ -42 +45,3 @@ Before you can establish a connection from your local Visual Studio Code to your - 1. In the SageMaker AI UI, navigate to your space +Use the following procedure to establish a connection using deep link. + + 1. [Launch Amazon SageMaker Studio](https://docs.aws.amazon.com/sagemaker/latest/dg/studio-updated-launch.html#studio-updated-launch-console). @@ -44 +49 @@ Before you can establish a connection from your local Visual Studio Code to your - 2. Choose **Open space with** + 2. In the Studio UI, navigate to your space. @@ -46 +51,3 @@ Before you can establish a connection from your local Visual Studio Code to your - 3. Choose **VS Code**. When you do so you may be prompted to **Open Visual Studio Code**. When you choose to do so, your local VS Code opens with another pop-up to confirm. Once completed, the remote connection established. + 3. Choose **Open space with**. + + 4. Choose **VS Code**. When you do so you may be prompted to **Open Visual Studio Code**. When you choose to do so, your local VS Code opens with another pop-up to confirm. Once completed, the remote connection established. @@ -53 +60 @@ Before you can establish a connection from your local Visual Studio Code to your -Use the information and instructions in [connect to AWS](https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/connect.html) in the Toolkit for VS Code user guide. +Use the following procedure to establish a connection using the AWS Toolkit for Visual Studio Code. @@ -59 +66,5 @@ Use the information and instructions in [connect to AWS](https://docs.aws.amazon - 3. In the AWS Explorer, expand **SageMaker AI**. + 3. [Connect to AWS](https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/connect.html). + + 4. In the AWS Explorer, expand **SageMaker AI**. + + 5. Find your Studio space. @@ -61 +72,3 @@ Use the information and instructions in [connect to AWS](https://docs.aws.amazon - 4. Find your Studio space. + 6. Choose the **Connect** icon next to your space to start it. + +###### Note @@ -63 +76,3 @@ Use the information and instructions in [connect to AWS](https://docs.aws.amazon - 5. Choose the **Connect** icon next to your space. + * Stop and restart the space in the Toolkit for Visual Studio to enable remote access, if not already connected. + + * If the space is not using a supported [instance size](https://docs.aws.amazon.com/sagemaker/latest/dg/remote-access.html#remote-access-instance-requirements), you will be asked to change the instance. @@ -69,0 +85,4 @@ Use the information and instructions in [connect to AWS](https://docs.aws.amazon +Use the following procedure to establish a connection using the SSH CLI. + +For this setup, ensure that you have the [AWS Command Line Interface (AWS CLI)](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) and the [Session Manager plugin for the AWS CLI](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html) installed. + @@ -149,9 +167,0 @@ If you need to use a [named AWS credential profile](https://docs.aws.amazon.com/ -###### Topics - - * [Connect to VPC with subnets without internet access](./remote-access-local-ide-setup-vpc-no-internet.html) - - * [Filter your Studio spaces](./remote-access-local-ide-setup-filter.html) - - - -