Skip to content

SYSTEM Cited by 1 source

AgentCore Memory

What it is

AgentCore Memory is the Bedrock AgentCore surface that provides built-in session state + shared memory across sub-agents + automatic context preservation through asynchronous processing workflows.

"AgentCore provides built-in session state management, shared memory across sub-agents, and automatic context preservation throughout asynchronous processing workflows." (Source: sources/2026-04-23-aws-modernizing-kyc-with-aws-serverless-solutions-and-agentic-ai)

"These agents operate within the AgentCore Runtime, sharing context through AgentCore Memory (a built-in feature of Bedrock AgentCore that automatically manages session state and context)..." (Source: same post.)

Why it exists

Multi-agent systems where the Supervisor dispatches several sub-agents on the same case need a shared scratchpad that every sub-agent sees — without forcing each sub-agent to receive the full case history as prompt context, and without re-prompting the Supervisor on every sub-agent turn.

Classical implementations of this (a shared DynamoDB table, an in-memory dict keyed by session id) need a lot of glue code: schema, eviction, per-agent write-scope, async safety. AgentCore Memory makes that the runtime's responsibility — sub-agents read / write a session-scoped context object that AgentCore persists and replays around async boundaries.

What the KYC architecture uses it for

  • Case context sharing: when the Document Analysis sub-agent extracts fields from a passport, the Identity Verification sub-agent can read those fields without being re-prompted with the raw image.
  • Asynchronous continuation: because MSK → Lambda → AgentCore is an async boundary, a single KYC case's execution may straddle multiple Lambda invocations. Memory keeps the session-scoped state alive across those hops.
  • Audit envelope seed: the same session state is presumably what feeds the comprehensive-context payload attached to a human-review escalation (the post mentions "escalates to human review with comprehensive context").

Pairing with the other AgentCore surfaces

  • systems/agentcore-gateway provides the tool-invocation path; Memory is the substrate through which tool-invocation outputs are shared.
  • systems/agentcore-identity authorises which agent can read / write the shared memory (implied by the post's "only authorized sub-agents can invoke specific tools and access the Knowledge Base").

Caveats

  • No internals disclosed. The KYC post describes Memory's responsibilities (session state, shared context, async-preservation) but not the representation (vector? key-value? document?), retention, size limits, or pricing.
  • Distinct from Bedrock Knowledge Bases. Knowledge Bases are the corpus-scoped RAG surface; Memory is the session-scoped shared state. The KYC post uses both, for distinct purposes.

Seen in

Last updated · 476 distilled / 1,218 read