AWS designs an AgentCore memory lifecycle with expiration, scoring, consolidation, and audit
Long-running agents need deliberate forgetting, plus traceable records for pruning, consolidation, and failures.
Key takeaways
AWS published an AgentCore memory lifecycle design on September 4 for long-running agents that accumulate stale context, reduce answer quality, and increase compliance risk. The post separates memory into episodic, semantic, and procedural types, then applies three policies: time-based expiration, relevance scoring, and model-assisted consolidation. Its deployable example runs nightly with EventBridge and Step Functions, invokes a sequence of Lambda functions, emits CloudWatch metrics, writes run results to Amazon S3, and routes failures to Amazon SNS. The numerical retention periods are examples rather than universal rules. Teams should define retention by purpose, legal basis, sensitivity, retrieval value, and rollback needs, then test that pruning improves freshness without deleting evidence or procedures that remain necessary.
Direct answer
AWS published an AgentCore memory lifecycle design on September 4 for long-running agents that accumulate stale context, reduce answer quality, and increase compliance risk. The post separates memory into episodic, semantic, and procedural types, then applies three policies: time-based expiration, relevance scoring, and model-assisted consolidation. Its deployable example runs nightly with EventBridge and Step Functions, invokes a sequence of Lambda functions, emits CloudWatch metrics, writes run results to Amazon S3, and routes failures to Amazon SNS. The numerical retention periods are examples rather than universal rules. Teams should define retention by purpose, legal basis, sensitivity, retrieval value, and rollback needs, then test that pruning improves freshness without deleting evidence or procedures that remain necessary.
Verified facts
AWS divides agent memory into episodic, semantic, and procedural categories. Conversation records are high-volume and usually decay quickly; distilled facts can remain useful longer; procedures are lower-volume but may carry the highest operational value.
The design combines time-based expiration, access and relevance scoring, and consolidation of lower-value records into compact semantic memory. Values such as a 90-day default are configurable starting points, not universal retention standards.
The reference architecture uses EventBridge to trigger Step Functions for pruning, scoring, consolidation, metrics, and result persistence. CloudWatch, S3, and SNS provide monitoring, audit output, and failure notification.
What changed
- Set retention by memory type
- Expire before scoring and consolidation
- Test quality and compliance before deletion
- Keep metrics and audit output for every run
Impact for AI users
Long-running agents can carry old preferences, resolved issues, or obsolete procedures into new tasks. Users should be able to inspect, correct, and delete memories about them. Operators need to know why a record was retained, when it was consolidated, who removed it, and whether required business or compliance evidence survives. More memory does not automatically make an agent more capable.
Operating checklist
- Inventory episodic, semantic, and procedural memory with purpose, sensitivity, owner, and deletion basis.
- Start with a time limit for low-risk episodic memory before adding scoring and consolidation.
- Use a golden question set to compare accuracy, stale references, recall, and complaints before and after cleanup.
- Record the input scope, policy version, deletion count, consolidation result, failures, and rollback point for every run.
AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance
FAQ
Is 90 days a standard retention period for agent memory?
No. It is a default in the example. Actual retention depends on purpose, regulation, sensitivity, and evidence requirements.
Why not delete every old memory?
Procedural knowledge and some semantic facts can remain valid. Unclassified deletion may reduce quality or remove audit evidence, so test and retain rollback.
How can a team prove that cleanup did not degrade the agent?
Compare accuracy, stale references, recall, and anomalies on a fixed question set, and retain the policy version and run result.
Summary
Agent memory should be governed as a data asset with retention limits, quality measures, and audit ownership; deliberate forgetting matters as much as recall.
This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.
What this means for everyday users
Long-running agents can carry old preferences, resolved issues, or obsolete procedures into new tasks. Users should be able to inspect, correct, and delete memories about them. Operators need to know why a record was retained, when it was consolidated, who removed it, and whether required business or compliance evidence survives. More memory does not automatically make an agent more capable.
Tools you may use
Related tutorials
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
AWS connects AgentCore evaluations to GitHub Actions for pre-merge agent regression gates
AWS published a reference workflow on September 8 for integrating Amazon Bedrock AgentCore Evaluations with GitHub Actions. The pipeline deploys a development agent and an OAuth-protected MCP server, invokes representative prompts, collects OpenTelemetry traces, and scores behavior before allowing a pull request to proceed. AWS describes built-in dimensions such as helpfulness, correctness, goal success, tool selection, tool parameters, and trajectory order, with custom and code-based evaluators available. The post compares three authentication patterns: evaluating stored traces, using a pre-authorized test user, or issuing machine-to-machine credentials for CI. Its implementation uses the third pattern. Teams should validate that CI credentials cannot escape their intended environment, that evaluation samples cover important failures, and that score variance, latency, evaluator cost, and rollback behavior are visible before treating the threshold as a release gate.
AWS Launches AgentCore Evaluations for Testing Any Agent Framework
AWS Launches AgentCore Evaluations for Testing Any Agent Framework. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: establishing repeatable offline evaluations, online monitoring, and human spot checks for an AI agent. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
AWS AgentCore Adds Cross-Account Knowledge Base Connections
AWS AgentCore Adds Cross-Account Knowledge Base Connections. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: enabling an AI agent to securely retrieve from a knowledge base in another account while verifying least-privilege access. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
AWS Bedrock AgentCore Gateway Brings Policy Controls to Agent Tool Access
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for AWS Bedrock AgentCore Gateway Brings Policy Controls to Agent Tool Access.
How to Choose AI Agent Tool Permissions: An AgentCore Dogwood Acceptance Guide
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for How to Choose AI Agent Tool Permissions: An AgentCore Dogwood Acceptance Guide.
GitHub Adds MCP Allowlists to Enterprise Managed Settings
GitHub announced on August 6, 2026 that MCP allowlists are available in enterprise managed settings. Administrators can define which MCP servers an organization may use instead of leaving every developer to make an isolated choice. The practical task is to confirm plan, policy, and client support, approve only audited servers, and test read-only requests that should be allowed or rejected. Keep the server identity, version, permissions, logs, credential rotation, and rollback path in the same record. An allowlist reduces accidental tool access, but it does not prove that a server is safe or that its data scope is minimal. Human approval remains necessary for sensitive changes and production actions.
