Strands Agents Memory (AWS)
https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/strands-sdk-memory.html
AWS code-first agent framework. Multi-LLM (Bedrock, Anthropic, Gemini, OpenAI). Memory via Mem0 integration (ElastiCache for Valkey + Neptune Analytics) or Bedrock AgentCore Memory. Local default uses FAISS; OpenSearch for production.
At a glance
- Type
- Mem0 + AgentCore-backed
- Tier
- T2
- Section
- Framework-embedded memory
- Created
- 2025-05 (Strands Agents SDK open-sourced May 2025)
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Strands SDK OSS free; memory via Bedrock AgentCore Memory: $0.25 per 1,000 short-term memory events; Runtime priced…
- Funding
- Amazon Web Services (subsidiary of Amazon); no independent funding
Taxonomy
- storage
- vector
- retrieval
- similarity
- persistence
- long-term
- update
- extraction
- unit
- fact
- governance
- opaque
- conflict
- llm-arbitrate
When to use
Optimised for: AWS Bedrock integration via code-first SDK
Anti-fit: not for non-AWS stacks
Pros & cons
Pros
AWS-native agent framework with first-class Mem0 integration — managed memory without extra ops.
Cons
AWS-only; tightly coupled to Bedrock/AgentCore; not portable to other clouds.
Claims & capabilities
Open-source SDK from AWS; integrates with Amazon Bedrock AgentCore Memory (SEMANTIC, SUMMARIZATION, USER_PREFERENCE strategies); used in production by Amazon Q Developer, AWS Glue, VPC Reachability Analyzer, and Smartsheet. AWS + Mem0 partnership brings persistent memory to next-gen Strands agents
Technical surface
- API surface
- SDK: Python (Agent + ConversationManager; Bedrock AgentCore Memory)
- Backend storage
- pluggable (AgentCore, Mem0)
- Deployment
- Both (OSS self-hosted; AWS Bedrock AgentCore managed cloud)
- Embedding model
- multiple supported
- Multi-tenancy
- namespace
- MCP
- native (first-party) — Strands MCP support
- A2A
- supported — Strands A2A server
- OpenTelemetry
- first-class — built-in OTel
Similar systems
Other framework-embedded memory in the catalog, ranked by inbound references.
- LangGraph Persistence T2
Distinct from LangMem. Built-in checkpointer saves graph state per super-step (short-term, thread-scoped). Store System adds long-term hierarchical key-value memory across threads with optional vector search + TTL. Postgres / Mongo / Redis stores for production.
- AutoGen Memory T2
ListMemory chronological context + teachable agents that vectorise corrections. Integrates with Mem0/Zep rather than building deep memory natively.
- CrewAI Memory T2
Memory subsystem inside the CrewAI orchestration framework; integrates with Mem0 for the long-term tier.
- AGiXT Adaptive Memory T2
Open-source AI automation platform. Routes between short-term and long-term memory adaptively across any LLM provider; plugin system for storage backends. Memory managed at the instruction-management layer — task context, instruction state, conversation history as unified agent state.
- Agno (Phidata) Memory T2
Agno (formerly Phidata). AgentStorage persists sessions to a DB; AgentMemory auto-classifies/store user preferences and conversation summaries. Single-line integrations with LanceDB, Pinecone, Weaviate, Qdrant.
- Botpress LLMz T1
Per-plan vector-DB storage quota + LLMz autonomous engine (in-session working memory) + Knowledge Base (semantic search over uploaded docs). Long-term user memory persists across sessions.
Related systems
References (5)
- Amazon Neptune Analytics builds on — Memory via Mem0 integration (ElastiCache for Valkey + Neptune Analytics)
- AWS Bedrock AgentCore Memory integrates with — ource SDK from AWS; integrates with Amazon Bedrock AgentCore Memory (SEMANTIC, SUMMARIZATION, USER_PREFERENCE strategies); used
- Bedrock AgentCore (AWS) depends on at runtime — adjacent-infrastructure cell: requires AWS; Bedrock + Mem0 / AgentCore Memory
- Mem0 integrates with — Memory via Mem0 integration (ElastiCache for Valkey + Neptune Analytics) or Bedrock AgentCore Memory. AWS+Mem0 partnership.
- Mem0 depends on at runtime — ni, OpenAI). Memory via Mem0 integration (ElastiCache for Valkey + Neptune Analytics) or Bedrock Age