# Amazon — Build memory-aware AI agents with Agentic Retrieve on Amazon Bedrock Managed Knowledge Base

- Company: Amazon (amazon.com)
- Announced: 2026-11-16T22:43:30+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/build-memory-aware-ai-agents-with-agentic-retrieve-on-amazon-bedrock-managed-knowledge-base/
- Record: https://forck.live/items/36947-build-memory-aware-ai-agents-with-agentic-retrieve-on-amazon-bedrock-managed
- Subject: Bedrock / Nova

Amazon Bedrock Managed Knowledge Base and AgentCore memory now handle conversation storage, fact extraction and retrieval for knowledge-grounded agents, so applications no longer persist history themselves. Developers turn it on by adding a memoryConfiguration to the AgenticRetrieveStream request, which makes AgentCore memory a retrieval source alongside the knowledge base. Within the same call the service restores the conversation, and the planner decides on its own when a fact about the user would help, retrieving it from long-term memory to compose the sub-queries it sends to the knowledge base. The same request carries a userContext, so the knowledge base returns only documents the user's access control lists allow, and the integration is opt-in and backward compatible. The post walks through an internal employee assistant for a fictional company, where staff sign in with Amazon Cognito and the ID token's sub claim identifies the user's memory while the verified email identifies the user to the ACL filter. It covers designing memory namespaces for many users, reading the trace to see when the planner used memory, and using AWS Identity and Access Management to enforce per-user memory isolation even when application code gets it wrong.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/build-memory-aware-ai-agents-with-agentic-retrieve-on-amazon-bedrock-managed-knowledge-base/:

> Users of a knowledge-grounded application expect it to remember them, not only to search well. They ask follow-up questions that make sense only in the context of the previous turn. They expect an answer about a policy or a procedure to reflect what they told the application about themselves last month. And they still expect every answer to be grounded in the documents they are allowed to read, with citations. Whether the application is a customer support assistant, a document chat inside a SaaS product, or an internal assistant over company policies, the expectation is the same.
> 
> Meeting that expectation is hard, because the context that would sharpen a search lives outside the knowledge base. A user’s location, role, or product tier was often mentioned in an unrelated conversation weeks ago. To use it, the application has to store every conversation, extract durable facts from it, decide which facts matter for the current question, and inject them into the request. When many users share the application, every one of those steps also has to be isolated per user, and so does every document.

---

Record: https://forck.live/items/36947-build-memory-aware-ai-agents-with-agentic-retrieve-on-amazon-bedrock-managed
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
