AWS bedrock-agentcore documentation change
Summary
Added trailing slashes to namespace examples in episodic memory documentation
Security assessment
Changes are formatting updates to namespace examples with no security context. No vulnerabilities or security features are mentioned.
Diff
diff --git a/bedrock-agentcore/latest/devguide/episodic-memory-strategy.md b/bedrock-agentcore/latest/devguide/episodic-memory-strategy.md index 873d98725..c8062cb3c 100644 --- a//bedrock-agentcore/latest/devguide/episodic-memory-strategy.md +++ b//bedrock-agentcore/latest/devguide/episodic-memory-strategy.md @@ -78 +78 @@ 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 +80 @@ 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 +82 @@ 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 +87 @@ 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 +89 @@ 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 +91 @@ 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.