AWS bedrock-agentcore documentation change
Summary
Formatting changes including typographical fixes, heading style changes, and removal of empty JSON policy placeholder
Security assessment
Changes include typographical fixes (apostrophes), heading formatting changes (###### to **), and removal of an empty JSON policy placeholder. The content about namespace organization for data isolation remains unchanged. No security vulnerabilities are addressed or new security features documented.
Diff
diff --git a/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.md b/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.md index bee6ac394..554abe94c 100644 --- a//bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.md +++ b//bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.md @@ -9 +9 @@ Restrict access with IAM -When you [create](./memory-create-a-memory-store.html) an AgentCore Memory, use a namespace to specify where the [long-term memories](./memory-types.html#memory-long-term-memory) for a [memory strategy](./memory-strategies.html) are logically grouped. Every time a new long-term memory is extracted using the memory strategy, it is saved under the namespace you set. This means that all long-term memories are scoped to their specific namespace, keeping them organized and preventing any mix-ups with other users or sessions. You should use a hierarchical format separated by forward slashes `/`. This helps keep memories organized clearly. As needed, you can choose to use the following pre-defined variables within braces in the namespace based on your application's organization needs: +When you [create](./memory-create-a-memory-store.html) an AgentCore Memory, use a namespace to specify where the [long-term memories](./memory-types.html#memory-long-term-memory) for a [memory strategy](./memory-strategies.html) are logically grouped. Every time a new long-term memory is extracted using the memory strategy, it is saved under the namespace you set. This means that all long-term memories are scoped to their specific namespace, keeping them organized and preventing any mix-ups with other users or sessions. You should use a hierarchical format separated by forward slashes `/` . This helps keep memories organized clearly. As needed, you can choose to use the following pre-defined variables within braces in the namespace based on your application’s organization needs: @@ -13 +13 @@ When you [create](./memory-create-a-memory-store.html) an AgentCore Memory, use -An actor refers to entity such as end users or agent/user combinations. For example, in a coding support chatbot, the actor is usually the developer asking questions. Using the actor ID helps the system know which user the memory belongs to, keeping each user's data separate and organized. +An actor refers to entity such as end users or agent/user combinations. For example, in a coding support chatbot, the actor is usually the developer asking questions. Using the actor ID helps the system know which user the memory belongs to, keeping each user’s data separate and organized. @@ -36 +36 @@ A namespace can have different levels of granularity: -###### Most granular Level of organization +**Most granular Level of organization** @@ -40 +40 @@ A namespace can have different levels of granularity: -###### Granular at the actor Level across sessions +**Granular at the actor Level across sessions** @@ -44 +44 @@ A namespace can have different levels of granularity: -###### Granular at the strategy Level across actors +**Granular at the strategy Level across actors** @@ -48 +48 @@ A namespace can have different levels of granularity: -###### Global across all strategies +**Global across all strategies** @@ -60,6 +59,0 @@ The following policy restricts access to retrieving memories to a specific names -JSON - - -**** - -