[opieter-aws]

Description

Documents the AgentCore Memory TypeScript integration (bedrock-agentcore/memory/strands) as a community page. The integration went GA in bedrock-agentcore v0.4.1, so it now belongs in the docs alongside the other AgentCore integrations.

It lands under Community → Memory Stores as the first memory-store catalog entry (the folder previously held only the overview). This is deliberately distinct from the existing community/session-managers/agentcore-memory page: that one is the Python AgentCore integration built as a session manager, whereas this one implements the Strands MemoryStore interface. The page is TypeScript-only because that is the only SDK this integration currently ships in.

Related Issues

None.

Documentation PR

This is the documentation change (under site/).

Type of Change

Documentation update

Testing

Built the site with npm run build (Astro production build, which runs the broken-link checker: 840 pages, no broken links) and confirmed the page renders with its community banner, the sidebar entry resolves, and the community catalog lists the row as TypeScript-only. Ran prettier --check on the changed files.

Checklist

• I have read the CONTRIBUTING document
• I have reviewed and understand every line of code in this PR, including any generated by AI tools, and I can explain why it works
• My change is focused and reasonably small; I have split unrelated work into separate PRs
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Assessment: Approve

Clean, well-scoped documentation PR. The new community page follows the established conventions and everything I could verify locally checks out.

Review notes

• Conventions: Frontmatter (project/service/maintainer, npm for the TS package) matches existing community pages like s3-vectors-memory.mdx; integrationType: memory-store is valid per the content schema, and the page will auto-populate the community catalog via getIntegrationEntries.
• Links & anchors: Internal links use the repo's .md extension convention with correct relative depth, and the #getting-started / #custom-stores anchors resolve to real headings in the memory overview.
• Tooling: prettier --check passes on both changed files; the nav entry is placed correctly under Community → Memory Stores.
• Minor (optional): sidebar.label duplicates title verbatim — most other community pages use a shorter distinct label, but this is harmless.
• Note: The subpath export (bedrock-agentcore/memory/strands) and API signatures live in the external SDK, so I relied on your verification for those.

Nicely done distinguishing this from the existing Python session-manager page — the "Notes" section on writable/eventual-consistency semantics is a helpful touch.

[github-actions]

Documentation Preview Ready

Your documentation preview has been successfully deployed!

Changed pages:

• community/memory-stores/agentcore-memory-store

Updated at: 2026-07-17T19:21:37.757Z

[github-actions]

Re-reviewed after the address feedback commit — the revisions from @gautamsirdeshmukh's review are all incorporated accurately:

• "Placeholders resolve at construction" (was "at write time"), now clarified as substituted client-side into the namespace used for recall. ✓
• Configuration now leads with a paragraph distinguishing per-namespaces options (namespace/writable/minScore) from the flat config accepted by the direct AgentCoreMemoryStore constructor. ✓
• "One writable store per session" now correctly scopes the throw to createAgentCoreMemoryStores and explains why (namespace-free writes would emit duplicate events to the same stream) — which implicitly signals the direct path is the caller's responsibility. ✓

prettier --check still passes. Assessment remains Approve — the clarifications materially improve accuracy.