From the source
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.






