- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello,
To retain the conversation context of an Amazon Bedrock agent after the session expires, you can use session state attributes. There are two types of session state attributes:
- SessionAttributes
- PromtSessionAttributes
Refer the below link for more info https://docs.aws.amazon.com/bedrock/latest/userguide/agents-session-state.html
Additionally, you can view the conversation history by enabling tracing for the InvokeAgent call. The trace tracks the agent's actions, queries and observations at each step, including context passed between prompts.****
Hi,
You may want to read this deck of this presentation of last re:Invent: Build a WebSocket API with conversation history for Amazon Bedrock
The deck is here: https://d1.awsstatic.com/events/Summits/reinvent2023/FWM311_Build-a-WebSocket-API-with-conversation-history-for-Amazon-Bedrock.pdf
Also, read in depth this blog post. It shows how to store conversations for agends in DynamoDB: https://aws.amazon.com/blogs/machine-learning/build-generative-ai-agents-with-amazon-bedrock-amazon-dynamodb-amazon-kendra-amazon-lex-and-langchain/
Best,
Didier
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
Hi, can you elaborate how I can get the conversation history using a session attribute and send it to Lambda function? In the documentation example the parameters are requested from user, while I just need a log of questions from users and generated answers.