AWS First Steps
New feature

Amazon Bedrock AgentCore Memory now supports extracting memories from non-conversational JSON payloads

Amazon Bedrock AgentCore Memory now processes JSON payloads directly via the CreateEvent API, enabling long-term memory extraction from structured data

Amazon Bedrock AgentCore Memory now accepts JSON payloads through the CreateEvent API, allowing agents to extract long-term memories from structured data such as behavioral events, activity logs, and system events (up to 100 KB per payload) without reformatting them into synthetic conversations. The extraction pipeline treats JSON payloads like conversations, generating long-term memories across all four strategies: semantic, user preference, summarization, and episodic. This capability is available in all regions where AgentCore Memory is supported and works seamlessly with existing features. To begin, simply include JSON payloads in your events.

Why it matters

This update benefits developers who want to use structured data for long-term memory and AI agent developers. Amazon Bedrock AgentCore helps manage AI agent memory, and this feature simplifies extracting knowledge from non-conversational data.

Read the original AWS announcement

Related articles and terms

Amazon BedrockA fully managed generative AI service providing access to leading foundation models via APIGenerative AI Platform - Building an Enterprise AI Foundation with Amazon BedrockLearn how to build generative AI applications using Amazon Bedrock. This guide covers foundation model selection, RAG pattern implementation, safety guardrails, and SageMaker integration for designing enterprise-grade AI infrastructure.AWS CloudTrailA service that records and monitors API activity in your AWS accountAmazon EventBridge PipesA service that builds point-to-point integrations from source to target with built-in filtering and transformationWhy Lambda's Limit Is 15 Minutes - The Rationale Behind Serverless Design ConstraintsThis article explains why Lambda's various limits - 15-minute maximum execution time, 10GB memory cap, 6MB payload - are set at those specific values, from the perspective of Firecracker's design philosophy and multi-tenant operations.