AWS sagemaker-unified-studio documentation change
Summary
Added documentation about enabling/disabling chat history and added warning about chat history integrity in preview
Security assessment
The change introduces a warning about chat history integrity and advises against using it for compliance/critical decisions. While this highlights potential reliability issues, there's no evidence of addressing a specific security vulnerability.
Diff
diff --git a/sagemaker-unified-studio/latest/adminguide/amazon-bedrock.md b/sagemaker-unified-studio/latest/adminguide/amazon-bedrock.md index 4803627e5..65a0a81cf 100644 --- a//sagemaker-unified-studio/latest/adminguide/amazon-bedrock.md +++ b//sagemaker-unified-studio/latest/adminguide/amazon-bedrock.md @@ -5 +5 @@ -Configure access to your Amazon Bedrock serverless models for the selected AWS accounts and regionsSet default models for the generative AI playgrounds in Amazon SageMaker Unified StudioPublishing models from associated accounts +Configure access to your Amazon Bedrock serverless models for the selected AWS accounts and regionsEnable or disable chat historySet default models for the generative AI playgrounds in Amazon SageMaker Unified StudioPublishing models from associated accounts @@ -49,0 +50,2 @@ Once Amazon Bedrock in SageMaker Unified Studio for a domain is set up, you can + * Enable or disable chat history + @@ -85,0 +88,8 @@ The following are important elements to consider as you review the generated lis +## Enable or disable chat history + +Chat history for the Amazon Bedrock in SageMaker Unified Studio chat playground is enabled by default. To disable chat history for your users, use the **Enable chat history** toggle in the **Chat history section** of the **Playground settings**. + +###### Important + +Chat history for the Amazon Bedrock in SageMaker Unified Studio playground is in preview and should be used as a development aid rather than a definitive record of model behavior. While we strive to maintain accuracy in session records, the integrity of stored chat interactions cannot be guaranteed. Users and organizations should not rely on chat history for critical business decisions, compliance purposes, or official documentation. +