AWS Security ChangesHomeSearch

AWS bedrock-agentcore documentation change

Service: bedrock-agentcore · 2026-04-10 · Documentation low

File: bedrock-agentcore/latest/devguide/memory-get-started.md

Summary

Formatting changes including adding step numbers to CLI commands, adjusting TUI step numbering, moving deployment instruction, fixing path typo, and updating apostrophe characters from curly to straight quotes.

Security assessment

Changes are purely formatting and typographical corrections. No security vulnerabilities, configurations, or features are mentioned or modified. The path correction from `app/`MyAgent`/memory/session.py` to `app/MyAgent/memory/session.py` fixes a typo but doesn't relate to security.

Diff

diff --git a/bedrock-agentcore/latest/devguide/memory-get-started.md b/bedrock-agentcore/latest/devguide/memory-get-started.md
index 48a2d3310..c337e2a6e 100644
--- a//bedrock-agentcore/latest/devguide/memory-get-started.md
+++ b//bedrock-agentcore/latest/devguide/memory-get-started.md
@@ -63 +63 @@ Create memory with semantic strategy:
-AgentCore CLI
+###### Example
@@ -64,0 +65 @@ AgentCore CLI
+AgentCore CLI
@@ -67 +68 @@ AgentCore CLI
-    agentcore add memory --name CustomerSupportSemantic --strategies SEMANTIC
+  1.     agentcore add memory --name CustomerSupportSemantic --strategies SEMANTIC
@@ -73 +77 @@ Interactive
-Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
+  1. Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
@@ -75 +79 @@ Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
-  1. Enter the memory name:
+  2. Enter the memory name:
@@ -79 +83 @@ Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
-  2. Select the **Semantic** strategy, then confirm:
+  3. Select the **Semantic** strategy, then confirm:
@@ -82,0 +87 @@ Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
+Then run `agentcore deploy` to provision the memory in AWS.
@@ -86 +90,0 @@ Run `agentcore` to open the TUI, then select **add** and choose **Memory** :
-Then run `agentcore deploy` to provision the memory in AWS.
@@ -145 +149 @@ The memory resource id, actor id, and session id are required to create an event
-You can get events (turns) for a specific actor after they've been written.
+You can get events (turns) for a specific actor after they’ve been written.
@@ -197 +201 @@ If you created a Strands agent without memory and want to add it later, follow t
-  3. Create `app/`MyAgent`/memory/session.py`:
+  3. Create `app/MyAgent/memory/session.py` :
@@ -253 +257 @@ If you created a Strands agent without memory and want to add it later, follow t
-Each memory resource gets an environment variable `MEMORY_`<NAME>`_ID` (uppercase, with underscores) that is automatically available in your agent's runtime environment after deployment.
+Each memory resource gets an environment variable `MEMORY_<NAME>_ID` (uppercase, with underscores) that is automatically available in your agent’s runtime environment after deployment.
@@ -257 +261 @@ Each memory resource gets an environment variable `MEMORY_`<NAME>`_ID` (uppercas
-When you're done with the memory resource, you can delete it:
+When you’re done with the memory resource, you can delete it: