AWS adds AgentCore memory to Bedrock Agentic Retrieve
AWS says Amazon Bedrock Managed Knowledge Base can now use Amazon Bedrock AgentCore memory within the same AgenticRetrieveStream request. The integration stores and restores conversations, extracts durable facts, and adds relevant memories to knowledge-base retrieval while retaining per-user isolation and ACL-based document filtering. Developers enable it with memoryConfiguration, while the service manages conversation persistence and fact extraction.
AWS says the managed integration reduces the need for applications to build separate conversation stores, history replay, and fact-extraction pipelines for memory-aware AI agents.
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.
#Amazon Bedrock Managed Knowledge Base#Amazon Bedrock AgentCore#Amazon Bedrock AgentCore memory#AgenticRetrieveStream#AWS IAM#Amazon Cognito