AMAZON BEDROCK / SERVICE DETAIL S07 (TOOLS)
AGENTCORE BROWSER
CHAPTER 17 / 36
IN ONE LINE a real web browser the agent can drive
REV 2026.07
A lot of work lives behind a website with no API: a supplier portal, a form, a dashboard. Browser gives the agent a real, managed web browser in the cloud that it can drive, click, type, read, screenshot, so it can use those sites like a person would, safely and on its own.
New to these words? Read chapter 02 "Key terms" (session, microVM, tool).
[ 1 ] WHAT IT IS
Browser is a managed Chrome browser in the cloud that the agent controls. It opens pages, clicks, fills forms, takes screenshots, and reads what is on screen, so an agent can use websites that have no API. It is built in to AgentCore and runs isolated, away from your machines.
THE AGENT GETS
A real browser it can drive step by step, plus screenshots so it can see the page.
A HUMAN CAN
Watch live and take over at any moment, then hand control back.
[ 2 ] HOW A SESSION WORKS
STEP 01
CREATE
Use the built-in browser (aws.browser.v1) or a custom one (your network, recording, permissions).
==>
STEP 02
START SESSION
Open a session: 15 minutes by default, up to 8 hours.
==>
STEP 03
DRIVE
The agent acts through the Automation stream: navigate, click, type, screenshot. Use Strands, Nova Act, or Playwright.
==>
STEP 04
WATCH
A person can open the Live View stream to watch in real time and take over.
==>
STEP 05
RECORD AND STOP
The session can be recorded to S3 for replay. Stop it to free resources.
[ 3 ] TWO LIVE STREAMS
AUTOMATION the agent acts
The agent sends actions: go to a page, click, type, screenshot.
This is how the agent does the actual work.
Driven by Strands, Nova Act, Playwright, or browser-use.
LIVE VIEW a human watches
A real-time video of the session.
A person can take control and give it back.
Good for oversight, and for steps that need a human (a login, a CAPTCHA).
[ 4 ] RECORDING, ISOLATION, AND LIMITS
RECORDING AND REPLAY
Custom browsers can be recorded to your S3 bucket (DOM changes, actions, network, console logs).
Replay them in the console, like a screen recording, for debugging and audit.
ISOLATION AND LIMITS
Each session runs in its own microVM, wiped at the end.
Default 15 minutes, up to 8 hours; up to 500 sessions at once; data kept 30 days.