AWS sagemaker-unified-studio high security documentation change
Summary
Added security note about persistent sessions in features (up to 12 hours) and updated VS Code extension version requirements
Security assessment
Explicitly warns about lingering sessions posing security risks on shared workstations/public networks. Directly addresses session management security concerns.
Diff
diff --git a/sagemaker-unified-studio/latest/adminguide/configuring-sagemaker-unified-studio-remote-access.md b/sagemaker-unified-studio/latest/adminguide/configuring-sagemaker-unified-studio-remote-access.md index 450009e21..8e440f8c4 100644 --- a//sagemaker-unified-studio/latest/adminguide/configuring-sagemaker-unified-studio-remote-access.md +++ b//sagemaker-unified-studio/latest/adminguide/configuring-sagemaker-unified-studio-remote-access.md @@ -10,0 +11,23 @@ Prerequisites +###### Note + +Certain features in Amazon SageMaker Unified Studio may maintain active sessions even after you log out of Amazon SageMaker Unified Studio or the associated IAM Identity Center/SSO session. Sometimes, these disconnected sessions can persist for up to 12 hours. Affected features include: + + * Spaces + + * Local IDE (Visual Studio Code) Support + + * Workflows + + * ML Experiments (MLFlow) + + * Connections + + * Hyperpod + + * Amazon SageMaker partner applications + + + + +To ensure the security of your environment, administrators must review and adjust session duration settings where possible and be cautious when using shared workstations or public networks. + @@ -40 +63 @@ To establish a remote connection from VS Code to a Amazon SageMaker Unified Stud - * VS Code with Microsoft Remote SSH (version 0.74.0 or later), and AWS Toolkit (version 3.74.0) extension installed on your local machine. + * VS Code with Microsoft Remote SSH (version 0.74.0 or higher), and AWS Toolkit (version 3.87.0 or higher) extension installed on your local machine.