AWS sagemaker documentation change
Summary
Updated terminology from 'local Visual Studio Code' to 'Remote IDE' in filter setup documentation.
Security assessment
The change is purely terminological to reflect broader IDE support. There is no evidence of security fixes, vulnerabilities, or new security features being documented; it only updates references to the connection method.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup-filter.md b/sagemaker/latest/dg/remote-access-remote-setup-filter.md index 98114162c..db3b8c92d 100644 --- a//sagemaker/latest/dg/remote-access-remote-setup-filter.md +++ b//sagemaker/latest/dg/remote-access-remote-setup-filter.md @@ -11 +11 @@ Users can filter spaces in the AWS Toolkit for Visual Studio Code explorer to di -This setup only applies when using the [Method 2: AWS Toolkit for Visual Studio Code](./remote-access-local-ide-setup.html#remote-access-local-ide-setup-local-vs-code-method-2-aws-toolkit-in-vs-code) method to connect from local Visual Studio Codes to Amazon SageMaker Studio spaces. See [Set up remote access](./remote-access-remote-setup.html) for more information. +This setup only applies when using the [Method 2: AWS Toolkit in the Remote IDE](./remote-access-local-ide-setup.html#remote-access-local-ide-setup-local-vs-code-method-2-aws-toolkit-in-vs-code) method to connect from your Remote IDE to Amazon SageMaker Studio spaces. See [Set up remote access](./remote-access-remote-setup.html) for more information. @@ -91 +91 @@ Set up private subnet with no internet access -Set up local Visual Studio Code +Set up Remote IDE