chore(memory): Restructure memory tutorial samples#1440
Draft
akshseh wants to merge 7 commits intoawslabs:mainfrom
Draft
chore(memory): Restructure memory tutorial samples#1440akshseh wants to merge 7 commits intoawslabs:mainfrom
akshseh wants to merge 7 commits intoawslabs:mainfrom
Conversation
Introduce a concepts primer, a CLI-vs-boto3-vs-AgentCore-SDK decision guide, and three quickstart placeholders that will walk the same end-to-end flow through each surface. Also checks in journal.md documenting the restructure plan.
- Renumber single-agent and multi-agent folders to 02- and 03- to make room for 01-core-features/ (framework-agnostic primitives: events & sessions, metadata filtering, actor/session isolation, event branching — placeholders for now). - Fold 04-memory-branching/ into the framework folders it belongs with: travel-planner branching under single-agent Strands, parallel multi-agent branching under multi-agent Strands. - Refresh the section README to show framework x pattern coverage and link to the new primitives.
- Renumber single-agent and multi-agent to 02- and 03- to make
room for 01-core-features/ (framework-agnostic primitives:
four built-in strategies, overrides, self-managed, namespaces,
retrieval, metadata, batch APIs, redrive, record streaming).
- Reshape framework folders into the three patterns: built-in
hook/callback/memory-block, custom, memory-as-tool. Notebooks
keep their original filenames to preserve history.
- Strands: split customer-support into built-in vs custom;
self-managed variants move under custom hook; memory-tool
folder merges into the 03-memory-tool pattern slot.
- LangGraph: nutrition assistants move under 02-custom-callback.
- LlamaIndex: domain examples consolidate under 03-memory-tool;
built-in and custom memory-block slots reserved as gaps.
- Multi-agent Strands: travel-booking under built-in hook,
healthcare (episodic) under custom hook.
- Pull memory-record streaming notebook out of 03-advanced-patterns
and into 01-core-features/09-record-streaming.ipynb — streaming
is a primitive; the downstream *use cases* stay in advanced.
- Refresh the LTM README plus per-framework READMEs to show
coverage, patterns, and gaps.
- Renumber: runtime (was 02) -> 01, identity-runtime (was 03) -> 02, guardrails (was 01) -> 03, memory-browser stays at 04. - Group the two streaming-derived tutorials into a new 05-streaming-use-cases/ folder: cross-region replication (from old 06/) becomes 01-; personalised-recommendations and cross-customer-analytics (from old 07/) become 02- and 03-. Streaming *primitive* itself moved to long-term memory core features in the prior commit. - Add a 06-observability.ipynb placeholder for CloudWatch metrics / logs across memory resources and streaming pipelines. - Add section README documenting the pattern and linking back to the streaming primitive as a prerequisite.
- Rename 05-memory-security-patterns/ -> 04-security-patterns/. - Rename 01-memory-iam-policies/ -> 01-iam-scoped-access/ and 02-memory-iam-cognito-identities/ -> 02-cognito-federated-identity/ to match the naming style used elsewhere. - Add 03-kms-encryption.ipynb placeholder for configuring a customer-managed key on a memory resource. - Rewrite root README to reflect the two-axis layout (memory type x features/frameworks) and explain why access surface (CLI / boto3 / AgentCore SDK) is a per-notebook decision, not a tree axis.
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
github-actions
Bot
added
01-tutorials
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Amazon Bedrock AgentCore Samples Pull Request
Important
review readylabel to it. Only PRs withreview readywill be reviewed.Issue number:
Concise description of the PR
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.