AWS sagemaker documentation change
Summary
Updated terminology from 'Remote IDE connections' to 'remote Visual Studio Code connections' or 'remote VS Code connections' to align with the narrowed IDE focus.
Security assessment
This change only updates terminology to reflect the narrowed IDE support (Visual Studio Code only). The ABAC security feature documentation remains, but this specific change doesn't add new security documentation or address a security issue.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup-abac.md b/sagemaker/latest/dg/remote-access-remote-setup-abac.md index 2301c0958..69604b0dd 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 IDE connections using ABAC policies. The following are example ABAC policies for Remote IDE 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 Visual Studio Code connections using ABAC policies. The following are example ABAC policies for remote VS Code connections.