AWS sagemaker documentation change
Summary
Updated documentation to focus exclusively on Visual Studio Code for remote access to SageMaker Studio spaces in private subnets without internet access, removing support and references to Kiro and Cursor IDEs.
Security assessment
The changes are documentation updates that clarify supported IDEs (now only VS Code) and streamline instructions. There is no mention of security vulnerabilities, patches, or incidents. The changes involve removing references to unsupported tools (Kiro, Cursor) and updating terminology from 'Remote IDE' to 'local Visual Studio Code'. While the context involves network security (private subnets, firewalls, proxies), the changes themselves are feature support updates, not security fixes.
Diff
diff --git a/sagemaker/latest/dg/remote-access-local-ide-setup-vpc-no-internet.md b/sagemaker/latest/dg/remote-access-local-ide-setup-vpc-no-internet.md index 2ee1509bc..4dc669d52 100644 --- a//sagemaker/latest/dg/remote-access-local-ide-setup-vpc-no-internet.md +++ b//sagemaker/latest/dg/remote-access-local-ide-setup-vpc-no-internet.md @@ -5 +5 @@ -HTTP Proxy with controlled allow-listingPre-packaged remote server and extensions (VS Code only) +HTTP Proxy with controlled allow-listingPre-packaged VS Code remote server and extensions @@ -9 +9 @@ HTTP Proxy with controlled allow-listingPre-packaged remote server and extension -Before connecting your Remote IDE to Studio spaces in private subnets without internet access, ensure your administrator has [Set up Studio to run with subnets without internet access within a VPC](./remote-access-remote-setup-vpc-subnets-without-internet-access.html). +Before connecting Visual Studio Code to Studio spaces in private subnets without internet access, ensure your administrator has [Set up Studio to run with subnets without internet access within a VPC](./remote-access-remote-setup-vpc-subnets-without-internet-access.html). @@ -11 +11 @@ Before connecting your Remote IDE to Studio spaces in private subnets without in -You have the following options to connect your Remote IDE to Studio spaces in private subnets: +You have two options to connect your local Visual Studio Code to Studio spaces in private subnets: @@ -13 +13 @@ You have the following options to connect your Remote IDE to Studio spaces in pr - * Set up HTTP Proxy (supported for VS Code and Kiro) + * Set up HTTP Proxy @@ -15 +15 @@ You have the following options to connect your Remote IDE to Studio spaces in pr - * Pre-packaged remote server and extensions (VS Code only) + * Pre-packaged VS Code remote server and extensions @@ -20,4 +19,0 @@ You have the following options to connect your Remote IDE to Studio spaces in pr -###### Important - -Cursor is not supported for connecting to Studio spaces in private subnets without outbound internet access. - @@ -28 +24 @@ Cursor is not supported for connecting to Studio spaces in private subnets witho - * Pre-packaged remote server and extensions (VS Code only) + * Pre-packaged VS Code remote server and extensions @@ -35,4 +31 @@ Cursor is not supported for connecting to Studio spaces in private subnets witho -When your Studio space is behind a firewall or proxy, ask your administrator to allow access to your IDE server and extension-related CDNs and endpoints. For more information, see [Set up HTTP Proxy with controlled allow-listing](./remote-access-remote-setup-vpc-subnets-without-internet-access.html#remote-access-remote-setup-vpc-subnets-without-internet-access-setup-http-proxy-with-controlled-allow-listing). - -VS Code - +When your Studio space is behind a firewall or proxy, ask your administrator to allow access to VS Code server and extension-related CDNs and endpoints. For more information, see [Set up HTTP Proxy with controlled allow-listing](./remote-access-remote-setup-vpc-subnets-without-internet-access.html#remote-access-remote-setup-vpc-subnets-without-internet-access-setup-http-proxy-with-controlled-allow-listing). @@ -40 +33 @@ VS Code -Configure the HTTP proxy for VS Code remote development by providing the proxy URL with the `remote.SSH.httpProxy` or `remote.SSH.httpsProxy` setting. +Once set up, you can configure the HTTP proxy for VS Code remote development by providing the proxy URL with the `remote.SSH.httpProxy` or `remote.SSH.httpsProxy` setting. @@ -44,14 +37 @@ Configure the HTTP proxy for VS Code remote development by providing the proxy U -Consider enabling "Remote.SSH: Use Curl And Wget Configuration Files" to use the configuration from the remote environment’s `curlrc` and `wgetrc` files. This is so that the `curlrc` and `wgetrc` files, placed in their respective default locations in the SageMaker space, can be used for enabling certain cases. - -Kiro - - -Configure the HTTP proxy for Kiro remote development by setting the `aws.sagemaker.ssh.kiro.httpsProxy` setting to your HTTP or HTTPS proxy endpoint. - -If you use MCP (Model Context Protocol) servers in Kiro, you also need to add the proxy environment variables to your MCP server configuration: - - - "env": { - "http_proxy": "${http_proxy}", - "https_proxy": "${https_proxy}" - } +Consider enabling “Remote.SSH: Use Curl And Wget Configuration Files” to use the configuration from the remote environment’s `curlrc` and `wgetrc` files. This is so that the `curlrc` and `wgetrc` files, placed in their respective default locations in the SageMaker space, can be used for enabling certain cases. @@ -61,5 +41 @@ This option works when you are allowed to set up HTTP proxy and lets you install -## Pre-packaged remote server and extensions (VS Code only) - -###### Note - -This option is only available for Visual Studio Code. Kiro and Cursor do not support pre-packaged remote server setup. +## Pre-packaged VS Code remote server and extensions @@ -67 +43 @@ This option is only available for Visual Studio Code. Kiro and Cursor do not sup -When your Studio spaces can’t access external endpoints to download VS Code remote server and extensions, you can pre-package them. With this approach, your administrator can export a tarball containing the `.VS Code-server` directory for a specific version of VS Code. Then, the administrator uses a SageMaker AI Lifecycle Configuration (LCC) script to copy and extract the tarball into your home directory (`/home/sagemaker-user`). For more information, see [Set up Pre-packaged remote server and extensions (VS Code only)](./remote-access-remote-setup-vpc-subnets-without-internet-access.html#remote-access-remote-setup-vpc-subnets-without-internet-access-setup-pre-packaged-vs-code-remote-server-and-extensions). +When your Studio spaces can’t access external endpoints to download VS Code remote server and extensions, you can pre-package them. With this approach, your administrator can export a tarball containing the `.VS Code-server` directory for a specific version of VS Code. Then, the administrator uses a SageMaker AI Lifecycle Configuration (LCC) script to copy and extract the tarball into your home directory (`/home/sagemaker-user`). For more information, see [Set up Pre-packaged Visual Studio Code remote server and extensions](./remote-access-remote-setup-vpc-subnets-without-internet-access.html#remote-access-remote-setup-vpc-subnets-without-internet-access-setup-pre-packaged-vs-code-remote-server-and-extensions). @@ -200 +176 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Set up Remote IDE +Set up local Visual Studio Code