AWS bedrock-agentcore documentation change
Summary
Formatting changes including converting headings from markdown '######' to bold text, adding example numbering, and minor typographical fixes (apostrophe correction).
Security assessment
Changes are purely presentational—adjusting heading styles, adding step numbers to CLI/SDK examples, and fixing typography. No security-related content was added, removed, or modified. The documentation still describes the same persistent filesystem feature without any security implications being introduced or addressed.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-persistent-filesystems.md b/bedrock-agentcore/latest/devguide/runtime-persistent-filesystems.md index 83c5ef0d4..8f4af91bd 100644 --- a//bedrock-agentcore/latest/devguide/runtime-persistent-filesystems.md +++ b//bedrock-agentcore/latest/devguide/runtime-persistent-filesystems.md @@ -9 +9 @@ How session storage worksConfigure session storageInvoke with session storageFil -Agents built on Amazon Bedrock AgentCore Runtime maintain their local state during the compute lifecycle and by default, the compute associated with a session is ephemeral. Every session boots into a clean filesystem, and if the session is stopped or terminated, invoking the same session again will get a new compute and a clean filesystem. Modern agents don't just chat — they write code, install packages, generate artifacts, and manage state through the filesystem. +Agents built on Amazon Bedrock AgentCore Runtime maintain their local state during the compute lifecycle and by default, the compute associated with a session is ephemeral. Every session boots into a clean filesystem, and if the session is stopped or terminated, invoking the same session again will get a new compute and a clean filesystem. Modern agents don’t just chat — they write code, install packages, generate artifacts, and manage state through the filesystem. @@ -32 +32 @@ Add `filesystemConfigurations` with a `sessionStorage` entry when creating or up -AWS CLI +###### Example @@ -33,0 +34 @@ AWS CLI +AWS CLI @@ -36 +37 @@ AWS CLI - aws bedrock-agentcore-control create-agent-runtime \ + 1. aws bedrock-agentcore-control create-agent-runtime \ @@ -50 +50,0 @@ AWS CLI -AWS SDK @@ -53 +53,2 @@ AWS SDK -Python example using boto3 to create an AgentCore Runtime with session storage. + +AWS SDK @@ -55,0 +57,2 @@ Python example using boto3 to create an AgentCore Runtime with session storage. + 1. Python example using boto3 to create an AgentCore Runtime with session storage. + @@ -83 +89 @@ Invoke the agent with a `runtimeSessionId`. Everything your agent writes to the -###### Example Using session storage across stop/resume cycles +**Example Using session storage across stop/resume cycles** @@ -105 +111 @@ The agent sees `/mnt/workspace` exactly as it left it. Source files, node_module -The session's compute environment spun down hours ago. But the filesystem was already persisted. When you resume, a new compute environment mounts the same storage, and your agent picks up mid-thought. +The session’s compute environment spun down hours ago. But the filesystem was already persisted. When you resume, a new compute environment mounts the same storage, and your agent picks up mid-thought. @@ -119 +125 @@ Session storage provides a standard Linux filesystem at your configured mount pa -###### Supported operations +**Supported operations** @@ -123 +129 @@ Regular files, directories, and symlinks. Read, write, rename, delete, `chmod`, -###### Limits +**Limits** @@ -127 +133 @@ For session storage limits including maximum storage size, file count, and direc -###### Unsupported operations +**Unsupported operations** @@ -176 +182 @@ This example shows a coding agent using Strands Agents with `FileSessionManager` -###### Coding agent with session storage +**Coding agent with session storage** @@ -219 +225 @@ This example shows a coding agent using Strands Agents with `FileSessionManager` -###### requirements.txt +**requirements.txt** @@ -229 +235 @@ Invoke the agent, stop the session, then resume. Both project files and conversa -###### Invoke, stop, and resume cycle +**Invoke, stop, and resume cycle**