AWS bedrock-agentcore documentation change
Summary
Added table of contents, changed heading formatting, removed redundant JSON code block markers, and updated text formatting (apostrophes).
Security assessment
Changes are organizational (adding TOC) and formatting (removing JSON markers, changing headings). The existing security documentation about microVM isolation and session security remains unchanged in content. No new security information was added or modified.
Diff
diff --git a/bedrock-agentcore/latest/devguide/browser-resource-session-management.md b/bedrock-agentcore/latest/devguide/browser-resource-session-management.md index 8f7848b08..30926da93 100644 --- a//bedrock-agentcore/latest/devguide/browser-resource-session-management.md +++ b//bedrock-agentcore/latest/devguide/browser-resource-session-management.md @@ -10,0 +11,13 @@ The following topics show how the Amazon Bedrock AgentCore Browser works and how +###### Topics + + * Creating a Browser Tool and starting a session + + * Resource management + + * [Using Browser Tool](./browser-using-tool.html) + + * [Managing Browser Sessions](./browser-managing-sessions.html) + + + + @@ -13 +26 @@ The following topics show how the Amazon Bedrock AgentCore Browser works and how - 1. ###### Create a Browser Tool + 1. **Create a Browser Tool** @@ -17 +30 @@ When configuring a Browser Tool, choose the public network setting, recording co - 2. ###### Start a session + 2. **Start a session** @@ -21 +34 @@ The Browser Tool uses a session-based model. After creating a Browser Tool, you - 3. ###### Interact with the browser + 3. **Interact with the browser** @@ -27 +40 @@ Meanwhile, the Live View endpoint allows an end user to watch the browser sessio - 4. ###### Stop the session + 4. **Stop the session** @@ -29 +42 @@ Meanwhile, the Live View endpoint allows an end user to watch the browser sessio -When you're finished using the browser session, you should stop it to release resources and avoid unnecessary charges. Sessions can be stopped manually or will automatically terminate after the configured timeout period. +When you’re finished using the browser session, you should stop it to release resources and avoid unnecessary charges. Sessions can be stopped manually or will automatically terminate after the configured timeout period. @@ -38,6 +50,0 @@ To use the Amazon Bedrock AgentCore Browser, you need the following permissions -JSON - - -**** - - @@ -69,2 +76 @@ JSON - -If you're using session recording with S3, the execution role you provide when creating a browser needs the following permissions: +If you’re using session recording with S3, the execution role you provide when creating a browser needs the following permissions: @@ -91,6 +96,0 @@ You should also add the following trust policy to the execution role: -JSON - - -**** - - @@ -215 +214 @@ AgentCore Tools enable isolation of each user session to ensure secure and consi -Each tool session runs in a dedicated microVM with isolated CPU, memory, and filesystem resources. This architecture guarantees that one user's tool invocation cannot access data from another user's session. Upon session completion, the microVM is fully terminated, and its memory is sanitized, thereby eliminating any risk of cross-session data leakage. +Each tool session runs in a dedicated microVM with isolated CPU, memory, and filesystem resources. This architecture guarantees that one user’s tool invocation cannot access data from another user’s session. Upon session completion, the microVM is fully terminated, and its memory is sanitized, thereby eliminating any risk of cross-session data leakage.