AWS sagemaker documentation change
Summary
Updated terminology from 'remote VS Code connections' to 'Remote IDE connections' to align with broader IDE support.
Security assessment
This is a minor terminology update to maintain consistency with the expanded IDE support. No security-related changes or documentation about security features were added. The change only updates the naming convention in ABAC policy examples.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup-abac.md b/sagemaker/latest/dg/remote-access-remote-setup-abac.md index ab5c66098..8154c37fe 100644 --- a//sagemaker/latest/dg/remote-access-remote-setup-abac.md +++ b//sagemaker/latest/dg/remote-access-remote-setup-abac.md @@ -9 +9 @@ Remote access enforcementTag-based access control -Amazon SageMaker AI supports [attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) to achieve fine-grained access control for remote Visual Studio Code connections using ABAC policies. The following are example ABAC policies for remote VS Code connections. +Amazon SageMaker AI supports [attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) to achieve fine-grained access control for Remote IDE connections using ABAC policies. The following are example ABAC policies for Remote IDE connections.