Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- AWS announced the feature on November 17, 2026. Memory resources with an existing summary strategy generate the recap automatically.
- The full recap is a long-term memory record in the same session namespace as the summary chunks. The documentation also covers older sessions that AWS previously summarized.
- Use ListMemoryRecords to filter by type in a known session. For semantic search, specify the same filter in searchCriteria when calling RetrieveMemoryRecords.
- Filtering by type controls the results. Full summaries share the memory resource ARN and read permissions with other records, so callers still need session-level authorization.
When should I read the recap or the chunks?
The full summary is a running recap of the session. It helps when handing over a support case or resuming a lengthy planning conversation. Chunks summarize batches of processed events and help locate details from particular stages.
Suppose a support agent takes over a return request. Read the full recap for the latest status, then check the relevant chunk for the pickup time discussed earlier. The recap is model-generated, so verify commitments and business status against the source of record.
How do I retrieve the recap for a known session?
Confirm that the memory uses a summary strategy and obtain trusted strategy, actor and session identifiers. The default namespace is /strategy/{memoryStrategyId}/actor/{actorId}/session/{sessionId}/. Use the resource’s configured namespace if you have a custom template.
In ListMemoryRecords, set an equality filter on the system metadata key x-amz-agentcore-memory-recordType with FULL_SESSION as its value. No manual indexing is needed. Use GetMemoryRecord when you already know the record ID. For semantic search with RetrieveMemoryRecords, put the same condition in metadataFilters inside searchCriteria.
If no record is returned, check the resource, strategy, actor, session and read permissions, then check whether a recap has been generated. Read it again after new events are written. The reviewed documentation does not specify an update delay.
Which Regions and permissions apply?
AWS says full summaries are available in Regions that offer AgentCore Memory. Existing summary strategies generate them automatically. The documentation also covers sessions that were summarized before the feature. Check the actual read result to confirm the record exists for your resource.
Full summaries share the same IAM read actions and resource ARN with other records in the memory. The application should restrict each caller to authorized sessions based on verified identity. FULL_SESSION selects the returned content and does not replace authorization.
AWS applies the same encryption at rest to these records. If the memory uses a customer-managed AWS KMS key, that key also encrypts full summaries.
How should I budget for storage and retrieval?
Start with long-term memory rates. AWS lists built-in long-term storage at $0.75 per 1,000 records per month and long-term retrieval at $0.50 per 1,000 retrievals. Check which charges apply to your strategy and usage.
The recap is a record stored alongside the chunks. Include session volume and reading frequency in your estimate. The announcement does not list a dedicated charge for generating or updating the recap. Use actual AWS usage details to confirm the bill.
Sources
Frequently Asked Questions
Do I have to index the record type as a custom field?
No. x-amz-agentcore-memory-recordType is a system metadata key. Filter for FULL_SESSION in the actual session namespace.
Does the raw event retention period also set the recap’s expiry?
The recap is stored as a long-term record. eventExpiryDuration applies to short-term raw events. Check the long-term memory lifecycle rules for the recap itself.