AWS sagemaker documentation change
Summary
Updated terminology from 'remote Visual Studio Code connections' to 'Remote IDE connections' in ABAC policy documentation.
Security assessment
This is a minor terminology update to align with broader IDE support. The change does not introduce, modify, or address any security policies, vulnerabilities, or incidents; it only updates the naming convention in existing ABAC documentation.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup-abac.md b/sagemaker/latest/dg/remote-access-remote-setup-abac.md index 69604b0dd..2301c0958 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.