AWS sagemaker documentation change
Summary
Updated terminology from 'local Visual Studio Code' to 'Remote IDE' throughout the document, and clarified that remote IDE connections (not just VS Code) maintain active sessions for up to 12 hours after IAM Identity Center logout.
Security assessment
The changes are primarily terminology updates to broaden the scope from Visual Studio Code to generic Remote IDE. The security warning about persistent sessions (up to 12 hours) after IAM Identity Center logout was already present and remains unchanged in substance. No new security vulnerabilities or incidents are addressed.
Diff
diff --git a/sagemaker/latest/dg/remote-access-remote-setup.md b/sagemaker/latest/dg/remote-access-remote-setup.md index 78a94d7f4..1fa43cfed 100644 --- a//sagemaker/latest/dg/remote-access-remote-setup.md +++ b//sagemaker/latest/dg/remote-access-remote-setup.md @@ -9 +9 @@ Step 1: Configure security and permissionsStep 2: Enable remote access for your -Before users can connect their local Visual Studio Code to Studio spaces, the administrator must configure permissions. This section provides instructions for administrators on how to set up their Amazon SageMaker AI domain with remote access. +Before users can connect their Remote IDE to Studio spaces, the administrator must configure permissions. This section provides instructions for administrators on how to set up their Amazon SageMaker AI domain with remote access. @@ -15 +15 @@ Different connection methods require different IAM permissions. Configure the ap -Currently remote IDE connections are authenticated using IAM credentials, not IAM Identity Center. This applies for domains that use the IAM Identity Center [authentication method](https://docs.aws.amazon.com/sagemaker/latest/dg/onboard-custom.html#onboard-custom-authentication-details) for your users to access the domain. If you prefer not to use IAM authentication for remote connections, you can opt-out by disabling this feature using the `RemoteAccess` conditional key in your IAM policies. For more information, see [Remote access enforcement](./remote-access-remote-setup-abac.html#remote-access-remote-setup-abac-remote-access-enforcement). When using IAM credentials, Local IDE (Visual Studio Code) connection may maintain active sessions even after you log out of your IAM Identity Center session. Sometimes, these Local IDE (Visual Studio Code) connection can persist for up to 12 hours. To ensure the security of your environment, administrators must review session duration settings where possible and be cautious when using shared workstations or public networks. +Currently remote IDE connections are authenticated using IAM credentials, not IAM Identity Center. This applies for domains that use the IAM Identity Center [authentication method](https://docs.aws.amazon.com/sagemaker/latest/dg/onboard-custom.html#onboard-custom-authentication-details) for your users to access the domain. If you prefer not to use IAM authentication for remote connections, you can opt-out by disabling this feature using the `RemoteAccess` conditional key in your IAM policies. For more information, see [Remote access enforcement](./remote-access-remote-setup-abac.html#remote-access-remote-setup-abac-remote-access-enforcement). When using IAM credentials, Remote IDE connections may maintain active sessions even after you log out of your IAM Identity Center session. Sometimes, these Remote IDE connections can persist for up to 12 hours. To ensure the security of your environment, administrators must review session duration settings where possible and be cautious when using shared workstations or public networks. @@ -185 +185 @@ After setup, users can run `ssh my_studio_space_abc` to start up the space. For -After you set up the permissions, you must toggle on **Remote Access** and start your space in Studio before the user can connect using their local VS Code. This setup only needs to be done once. +After you set up the permissions, you must toggle on **Remote Access** and start your space in Studio before the user can connect using their Remote IDE. This setup only needs to be done once.