AWS bedrock-agentcore documentation change
Summary
Major restructuring of documentation with sections reorganized and expanded. Added detailed information about system ARNs vs custom ARNs, session management characteristics (timeout, recording, live view, retention), and isolated sessions using microVMs for security.
Security assessment
The changes add significant security documentation about session isolation in microVMs with memory sanitization to prevent cross-session data leakage, which is a security feature. However, there is no evidence this addresses a specific security vulnerability or incident - it appears to be routine documentation enhancement and reorganization.
Diff
diff --git a/bedrock-agentcore/latest/devguide/browser-resource-session-management.md b/bedrock-agentcore/latest/devguide/browser-resource-session-management.md index 110b4268e..62623e4ba 100644 --- a//bedrock-agentcore/latest/devguide/browser-resource-session-management.md +++ b//bedrock-agentcore/latest/devguide/browser-resource-session-management.md @@ -5 +5 @@ -PermissionsBrowser setup for API operationsCreating a Browser Tool and starting a session +Creating a Browser Tool and starting a sessionResource management @@ -7 +7 @@ PermissionsBrowser setup for API operationsCreating a Browser Tool and starting -# Resource and session management +# Fundamentals @@ -11 +11,24 @@ The following topics show how the Amazon Bedrock AgentCore Browser works and how -## Permissions +## Creating a Browser Tool and starting a session + + 1. ###### Create a Browser Tool + +When configuring a Browser Tool, choose the public network setting, recording configuration for session replay, and permissions through an IAM runtime role that defines what AWS resources the Browser Tool can access. + + 2. ###### Start a session + +The Browser Tool uses a session-based model. After creating a Browser Tool, you start a session with a configurable timeout period (default is 15 minutes). Sessions automatically terminate after the timeout period. Multiple sessions can be active simultaneously for a single Browser Tool, with each session maintaining its own state and environment. + + 3. ###### Interact with the browser + +Once a session is started, you can interact with the browser using WebSocket-based streaming APIs. The Automation endpoint enables your agent to perform browser actions such as navigating to websites, clicking elements, filling out forms, taking screenshots, and more. Libraries like browser-use or Playwright can be used to simplify these interactions. + +Meanwhile, the Live View endpoint allows an end user to watch the browser session in real time and interact with it directly through the live stream. + + 4. ###### Stop the session + +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. + + + + +### Permissions @@ -96 +119 @@ JSON -## Browser setup for API operations +### Browser setup for API operations @@ -120 +143 @@ Run the following commands to set up your Browser Tool that is common to all con -## Creating a Browser Tool and starting a session +## Resource management @@ -122 +145 @@ Run the following commands to set up your Browser Tool that is common to all con - 1. ###### Create a Browser Tool +The AgentCore Browser provides two types of resources: @@ -124 +147 @@ Run the following commands to set up your Browser Tool that is common to all con -When configuring a Browser Tool, choose the public network setting, recording configuration for session replay, and permissions through an IAM runtime role that defines what AWS resources the Browser Tool can access. +System ARNs @@ -126 +148,0 @@ When configuring a Browser Tool, choose the public network setting, recording co - 2. ###### Start a session @@ -128 +150 @@ When configuring a Browser Tool, choose the public network setting, recording co -The Browser Tool uses a session-based model. After creating a Browser Tool, you start a session with a configurable timeout period (default is 15 minutes). Sessions automatically terminate after the timeout period. Multiple sessions can be active simultaneously for a single Browser Tool, with each session maintaining its own state and environment. +System ARNs are default resources pre-created for ease of use. These ARNs have default configuration with the most restrictive options and are available for all regions where Amazon Bedrock AgentCore is available. @@ -130 +152,7 @@ The Browser Tool uses a session-based model. After creating a Browser Tool, you - 3. ###### Interact with the browser +Field | Value +---|--- +ID | aws.browser.v1 +ARN | arn:aws:bedrock-agentcore:us-east-1:aws:browser/aws.browser.v1 +Name | Amazon Bedrock AgentCore Browser Tool +Description | AWS built-in browser for secure web browsing +Status | READY @@ -132 +160 @@ The Browser Tool uses a session-based model. After creating a Browser Tool, you -Once a session is started, you can interact with the browser using WebSocket-based streaming APIs. The Automation endpoint enables your agent to perform browser actions such as navigating to websites, clicking elements, filling out forms, taking screenshots, and more. Libraries like browser-use or Playwright can be used to simplify these interactions. +Custom ARNs @@ -134 +161,0 @@ Once a session is started, you can interact with the browser using WebSocket-bas -Meanwhile, the Live View endpoint allows an end user to watch the browser session in real time and interact with it directly through the live stream. @@ -136 +163 @@ Meanwhile, the Live View endpoint allows an end user to watch the browser sessio - 4. ###### Stop the session +Custom ARNs allow you to configure a browser tool with your own settings. You can choose the public network setting, recording configuration, security settings, and permissions through an IAM runtime role that defines what AWS resources the browser tool can access. @@ -138 +165,45 @@ 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. +### Network settings + +The AgentCore Browser supports the public network mode. This mode allows the tool to access public internet resources. This option enables integration with external APIs and services. + +### Session management + +The AgentCore Browser sessions have the following characteristics: + +Session timeout + + +Default: 900 seconds (15 minutes) + +Configurable: Can be adjusted when creating sessions, up to 8 hours + +Session recording + + +Browser sessions can be recorded for later review + +Recordings include network traffic and console logs + +Recordings are stored in an S3 bucket specified during browser creation + +Live view + + +Sessions can be viewed in real-time using the live view feature + +Live view is available at: /browser-streams/aws.browser.v1/sessions/{session_id}/live-view + +Automatic termination + + +Sessions automatically terminate after the configured timeout period + +Multiple sessions + + +Multiple sessions can be active simultaneously for a single browser tool. Each session maintains its own state and environment. There can be up to a maximum of 500 sessions. + +Retention policy + + +The time to live (TTL) retention policy for the session data is 30 days. @@ -139,0 +211 @@ When you're finished using the browser session, you should stop it to release re +#### Using isolated sessions @@ -140,0 +213 @@ When you're finished using the browser session, you should stop it to release re +AgentCore Tools enable isolation of each user session to ensure secure and consistent reuse of context across multiple tool invocations. Session isolation is especially important for AI agent workloads due to their dynamic and multi-step execution patterns. @@ -141,0 +215 @@ When you're finished using the browser session, you should stop it to release re +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. @@ -149 +223 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using AgentCore Browser with other libraries +Playwright @@ -151 +225 @@ Using AgentCore Browser with other libraries -Resource management +Using Browser Tool