AWS bedrock documentation change
Summary
Clarified memory session termination conditions for Bedrock agents
Security assessment
The change improves documentation clarity about session timeouts but contains no security-related content or references to vulnerabilities. It's a usability improvement.
Diff
diff --git a/bedrock/latest/userguide/agents-memory.md b/bedrock/latest/userguide/agents-memory.md index 33e551759..e88306b92 100644 --- a//bedrock/latest/userguide/agents-memory.md +++ b//bedrock/latest/userguide/agents-memory.md @@ -13 +13,10 @@ The conversational context is stored in the memory as sessions with each session -After you enable memory for your agent, the current session gets associated with a specific memory context when you invoke agent with same `sessionId` as the current session and with `endSessions` set to '`true`', or when the `idleSessionTimeout` configured for the agent has timed out. This memory context is given a unique memory identifier. Your agent uses the memory context to access and utilize the stored conversation history and conversation summaries to generate responses. +After you enable memory for your agent, the current session gets associated with a specific memory context when either of the following occurs: + + * You invoke the agent with the same `sessionId` as the current session and with `endSession` set to `true`. + + * The `idleSessionTimeout` configured for the agent has elapsed. + + + + +This memory context is given a unique memory identifier. Your agent uses the memory context to access and utilize the stored conversation history and conversation summaries to generate responses.