Back to News
ProductAI Understanding briefing

Amazon Bedrock adds memory‑aware agents with Agentic Retrieve for managed knowledge bases

AWS introduces Agentic Retrieve, letting Bedrock agents store conversation history, extract facts, and reuse them across sessions while respecting per‑user access controls.

4 min readRead the primary source
Source-provided image accompanying Amazon Bedrock adds memory‑aware agents with Agentic Retrieve for managed knowledge bases
Primary-source documentSource recorded
Publisher
aws.amazon.com
Source type
Primary document — an official announcement, paper, filing, or first-party page we read directly.
ContextUnderstand this in 60 seconds

Key terms

Memory (Agent Memory)
Stored context an AI agent uses across steps or sessions to improve continuity.
API (Application Programming Interface)
A structured way for one software system to send requests to and receive responses from another system.
Knowledge Base
A curated collection of documents or records used for retrieval, support automation, or grounding responses.

What happened

Amazon Bedrock now supports a memory‑aware agent capability called Agentic Retrieve. By adding a memoryConfiguration to an AgenticRetrieveStream request, developers can have Bedrock automatically store each turn of a conversation, extract durable facts, and pull relevant facts into subsequent queries. The feature works with Bedrock Managed , enabling per‑user ACL filtering and private, isolated memory namespaces. The blog post provides a step‑by‑step walkthrough building a multi‑tenant employee assistant that authenticates users via Amazon Cognito, enforces document access via ACLs, and isolates each user’s long‑term memory within a shared AgentCore memory resource.

Amazon Bedrock’s Managed now includes an optional memoryConfiguration that can be supplied to the AgenticRetrieveStream API. When enabled, the service restores a user’s prior conversation from AgentCore memory, lets the planner decide if a stored fact would improve the answer, retrieves that fact, and incorporates it into the sub‑queries sent to the knowledge base. After generating a response, the turn is saved back to memory.

The blog demonstrates a multi‑tenant employee assistant for a fictional company, AnyCompany. Employees sign in with Amazon Cognito; the Cognito ID token provides a stable sub claim (used as the actorId for memory) and a verified email (used for ACL filtering). Documents are stored in Amazon S3 with a global ACL file that maps S3 prefixes to allowed email addresses.

A single AgentCore memory resource is shared across all users, but isolation is achieved through namespace templates that include the actorId (e.g., "/anycompany/<sub>"). Two extraction strategies are described: a summary strategy that captures any fact mentioned in conversation, and a preference strategy that records explicit user preferences. The planner automatically decides when to invoke memory retrieval based on the current question.

The post also covers required IAM policies, role assumptions with session tags, and how to enforce per‑user memory isolation even if application code is compromised. It explains how to list sessions, retrieve conversation history, and delete a user’s memory records for compliance. Observability is supported via CloudWatch metrics and Bedrock AgentCore tracing.

Finally, the sample code and infrastructure scripts are provided in a GitHub repository, allowing developers to replicate the setup, test the end‑to‑end flow, and tear down resources when finished.

Source details: aws.amazon.com

Why it matters

The addition of built‑in memory to Bedrock agents addresses a long‑standing limitation of retrieval‑augmented generation: the inability to retain context beyond a single request. By handling conversation restoration, fact extraction, and memory persistence as a managed service, AWS removes the need for developers to build custom storage layers, reducing engineering effort and potential security gaps. Per‑user isolation and ACL‑aware retrieval also make the feature suitable for enterprise use cases where data privacy and compliance are critical, such as internal HR or sales assistants. This could accelerate adoption of AI‑driven knowledge assistants across large organizations and set a new baseline for “memory‑aware” agents in the cloud AI market.

Memory‑aware agents close the gap between single‑turn retrieval‑augmented generation and truly conversational assistants that can remember user‑specific facts over weeks or months, enabling more natural and personalized interactions.

By offering this as a managed service, AWS eliminates the need for custom databases, vector stores, or bespoke pipelines to persist and retrieve conversation context, lowering development costs and reducing security risks associated with mishandled user data.

Per‑user ACL enforcement ensures that sensitive corporate documents are only returned to authorized employees, addressing compliance concerns that have limited the deployment of AI assistants in regulated environments.

The feature’s integration with existing Bedrock guardrails and observability tools provides enterprises with the auditability required for internal governance and external regulatory scrutiny.

If widely adopted, this could set a new standard for cloud AI platforms, prompting competitors to introduce comparable managed memory capabilities, thereby accelerating the overall maturity of enterprise AI assistants.

Interactive Mechanism

Interactive Mechanism: How It Actually Works

Explore the underlying technology behind this development interactively.

Agent Lifecycle Stage:
1
User Intent & Planning: "Audit customer refund request #4092 and settle payment."
2
Tool Calling: Emits structured JSON call crm_get_transaction(id='4092').
3
Guardrail & Verification:Paused: High-value action requires human operator sign-off.
4
Final Settlement: Refund recorded, email receipt dispatched, and audit log stored.
Core takeaway: An AI agent is not just a language model—it is a closed loop of planning, tool invocation, and environment feedback. Production systems require self-healing retries and strict human approval guardrails.
Interactive Concept Check+10 Points
What is AI? Quiz

A route planner searches possible journeys using explicit rules. What does this illustrate about AI?

What to watch next

Watch for developer adoption metrics, pricing details, and any limits on memory size or retention that AWS may publish. Integration with Bedrock guardrails and observability tools will be key for enterprises concerned about compliance and auditability. Competitors may respond with similar managed memory offerings, so the feature could spark a broader shift toward built‑in, privacy‑preserving agent memory in cloud AI services.

Pricing and quota information for AgentCore memory (storage size, retention periods, request rates) to understand cost implications for large‑scale deployments.

Limits on the number of concurrent memory namespaces or the size of extracted records, which could affect scalability for organizations with thousands of users.

Future enhancements such as real‑time memory updates, richer extraction strategies, or tighter integration with third‑party identity providers beyond Cognito.

Customer case studies or benchmark results that demonstrate performance, latency, and accuracy improvements when using memory‑aware retrieval versus stateless approaches.

Responses from other cloud AI providers (e.g., Google Vertex AI, Microsoft Azure AI) that may introduce similar managed memory services, influencing competitive dynamics.

Related guides & quizzes

Found this useful?