AWS sagemaker documentation change
Summary
Updated documentation to expand support from Visual Studio Code to multiple Remote IDEs (VS Code, Kiro, Cursor) for connecting to SageMaker Studio spaces in private subnets without internet access. Added IDE support table, Kiro-specific network requirements, and clarified which connection methods are supported for each IDE.
Security assessment
The changes primarily expand IDE support and clarify network requirements for remote development in isolated environments. While the documentation covers secure network configurations (private subnets, firewalls, proxies), there is no evidence of addressing a specific security vulnerability or incident. The updates are feature/enhancement documentation.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup-vpc-subnets-without-internet-access.md b/sagemaker/latest/dg/remote-access-remote-setup-vpc-subnets-without-internet-access.md index 86d1c1357..f28996124 100644 --- a//sagemaker/latest/dg/remote-access-remote-setup-vpc-subnets-without-internet-access.md +++ b//sagemaker/latest/dg/remote-access-remote-setup-vpc-subnets-without-internet-access.md @@ -9 +9 @@ Studio remote access network requirementsSetup Studio remote access network -This guide shows you how to connect to Amazon SageMaker Studio spaces from Visual Studio Code when your Amazon SageMaker AI domain runs in private subnets without internet access. You’ll learn about connectivity requirements and setup options to establish secure remote connections in isolated network environments. +This guide shows you how to connect to Amazon SageMaker Studio spaces from your Remote IDE when your Amazon SageMaker AI domain runs in private subnets without internet access. You’ll learn about connectivity requirements and setup options to establish secure remote connections in isolated network environments. @@ -12,0 +13,13 @@ You can configure Amazon SageMaker Studio to run in VPC only mode with subnets w +**IDE support for private subnet connections** + +The following table shows the supported connection methods for each Remote IDE when connecting to Studio spaces in private subnets without internet access. + +Connection method | VS Code | Kiro | Cursor +---|---|---|--- +HTTP Proxy support | Supported | Supported | Not supported +Pre-packaged remote server and extensions | Supported | Not supported | Not supported + +###### Important + +Cursor is not supported for connecting to Studio spaces in private subnets without outbound internet access. + @@ -24 +37 @@ You can configure Amazon SageMaker Studio to run in VPC only mode with subnets w -**VPC mode limitations** Studio in VPC mode only supports private subnets. Studio cannot work with subnets directly attached with an Internet Gateway (IGW). Remote VS Code connections share the same limitations as SageMaker AI. For more information, see [Connect Studio notebooks in a VPC to external resources](https://docs.aws.amazon.com/sagemaker/latest/dg/studio-notebooks-and-internet-access.html). +**VPC mode limitations** Studio in VPC mode only supports private subnets. Studio cannot work with subnets directly attached with an Internet Gateway (IGW). Remote IDE connections share the same limitations as SageMaker AI. For more information, see [Connect Studio notebooks in a VPC to external resources](https://docs.aws.amazon.com/sagemaker/latest/dg/studio-notebooks-and-internet-access.html). @@ -115,0 +129,13 @@ Remote VS Code connection requires VS Code remote development, which needs speci +**Kiro specific network requirements** + +Remote Kiro connection requires Kiro remote development, which needs specific network access to install the remote server and extensions. For firewall and proxy server configuration, see [Kiro firewall configuration](https://kiro.dev/docs/privacy-and-security/firewalls/). The requirements are similar to VS Code: + + * Access to Kiro server endpoints is needed to install and update the Kiro remote server. + + * Access to extension marketplace and related CDN endpoints is required for installing Kiro extensions through the extension panel. + + * Some extensions may require access to additional endpoints for downloading their specific dependencies. See the extension’s documentation for their specific connectivity requirements. + + + + @@ -118 +144 @@ Remote VS Code connection requires VS Code remote development, which needs speci -Your have two options to connect your local Visual Studio Code to Studio spaces in private subnets: +You have the following options to connect your Remote IDE to Studio spaces in private subnets: @@ -120 +146 @@ Your have two options to connect your local Visual Studio Code to Studio spaces - * HTTP Proxy + * HTTP Proxy (supported for VS Code and Kiro) @@ -122 +148 @@ Your have two options to connect your local Visual Studio Code to Studio spaces - * Pre-packaged VS Code remote server and extensions + * Pre-packaged remote server and extensions (VS Code only) @@ -129 +155 @@ Your have two options to connect your local Visual Studio Code to Studio spaces -When your Studio space is behind a firewall or proxy, allow access to VS Code server and extension-related CDNs and endpoints. +When your Studio space is behind a firewall or proxy, allow access to your IDE server and extension-related CDNs and endpoints. @@ -138 +164,5 @@ When your Studio space is behind a firewall or proxy, allow access to VS Code se -### Set up Pre-packaged Visual Studio Code remote server and extensions +### Set up 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.