AWS bedrock-agentcore documentation change
Summary
Updated heading formatting, added 'Topics' section with navigation links, fixed namespace syntax from backticks to inline code, and made typographical corrections
Security assessment
These changes improve documentation structure and fix formatting issues. The namespace syntax changes (from `/strategy/`{memoryStrategyId}`/` to `/strategy/{memoryStrategyId}/`) are formatting corrections, not security-related modifications. No security vulnerabilities are addressed, and no new security features are documented. The added 'Topics' section improves navigation but doesn't add security content.
Diff
diff --git a/bedrock-agentcore/latest/devguide/episodic-memory-strategy.md b/bedrock-agentcore/latest/devguide/episodic-memory-strategy.md index c8062cb3c..94aa7f1ec 100644 --- a//bedrock-agentcore/latest/devguide/episodic-memory-strategy.md +++ b//bedrock-agentcore/latest/devguide/episodic-memory-strategy.md @@ -21 +21 @@ When you invoke the episodic strategy, AgentCore automatically detects episode c -###### Steps in the strategy +**Steps in the strategy** @@ -34 +34 @@ The episodic memory strategy includes the following steps: -###### Strategy output +**Strategy output** @@ -38 +38 @@ The episodic memory strategy returns XML-formatted output for both episodes and -###### Examples of episodes captured by this strategy +**Examples of episodes captured by this strategy** @@ -42 +42 @@ The episodic memory strategy returns XML-formatted output for both episodes and - * An appointment rescheduling task that captured the user's intent, the agent's decision to use a particular tool, and the successful outcome. + * An appointment rescheduling task that captured the user’s intent, the agent’s decision to use a particular tool, and the successful outcome. @@ -51 +51 @@ The episodic strategy includes memory extraction and consolidation steps (shared -###### Examples of reflections include +**Examples of reflections include** @@ -67,0 +68,11 @@ By referencing stored episodes, your agent can retrieve relevant past experience +###### Topics + + * Namespaces + + * How to best retrieve episodes to improve agentic performance + + * [System prompts for episodic memory strategy](./memory-episodic-prompt.html) + + + + @@ -78 +89 @@ Episodes are commonly stored in one of the following namespaces: - * `/strategy/`{memoryStrategyId}`/` – Store episodes at the strategy level. Episodes that have different actors or that come from different sessions, but that belong to the same strategy, are stored in the same namespace. + * `/strategy/{memoryStrategyId}/` – Store episodes at the strategy level. Episodes that have different actors or that come from different sessions, but that belong to the same strategy, are stored in the same namespace. @@ -80 +91 @@ Episodes are commonly stored in one of the following namespaces: - * `/strategy/`{memoryStrategyId}`/actor/`{actorId}`/` – Store all episodes at the actor level. Episodes that come from different sessions, but that belong to the same actor, are stored in the same namespace. + * `/strategy/{memoryStrategyId}/actor/{actorId}/` – Store all episodes at the actor level. Episodes that come from different sessions, but that belong to the same actor, are stored in the same namespace. @@ -82 +93 @@ Episodes are commonly stored in one of the following namespaces: - * `/strategy/`{memoryStrategyId}`/actor/`{actorId}`/session/`{sessionId}`/` – Store all episodes at the session level. Episodes that belong to the same session are stored in the same namespace. + * `/strategy/{memoryStrategyId}/actor/{actorId}/session/{sessionId}/` – Store all episodes at the session level. Episodes that belong to the same session are stored in the same namespace. @@ -87 +98 @@ Episodes are commonly stored in one of the following namespaces: -Reflections must match the same namespace pattern as episodes, but reflections can be less nested. For example, if your episodic namespace is `/strategy/`{memoryStrategyId}`/actor/`{actorId}`/`, you can use the following namespaces for reflections: +Reflections must match the same namespace pattern as episodes, but reflections can be less nested. For example, if your episodic namespace is `/strategy/{memoryStrategyId}/actor/{actorId}/` , you can use the following namespaces for reflections: @@ -89 +100 @@ Reflections must match the same namespace pattern as episodes, but reflections c - * `/strategy/`{memoryStrategyId}`/actor/`{actorId}`/` – Insights will be extracted across all episodes for an actor. + * `/strategy/{memoryStrategyId}/actor/{actorId}/` – Insights will be extracted across all episodes for an actor. @@ -91 +102 @@ Reflections must match the same namespace pattern as episodes, but reflections c - * `/strategy/`{memoryStrategyId}`/` – Insights will be extracted across all episodes and across all actors for the strategy. + * `/strategy/{memoryStrategyId}/` – Insights will be extracted across all episodes and across all actors for the strategy.