What AWS AgentCore Browser supplies
Amazon Bedrock AgentCore Browser provides isolated managed browser sessions with live interaction and AWS observability. Browser automation libraries use its streaming endpoints; the surrounding AWS execution layer is a separate choice.
Your application already uses AWS identity, logging and storage, and browser workflows need to fit those systems.
This is a source-based buying guide, not a claim of hands-on testing across every documented feature. Follow the source for the product and plan you would actually use.
Sources: docs.aws.amazon.com ↗
Browser control
AWS AgentCore Browser: Create or select a Browser Tool, then start an isolated browser session. The documented default session timeout is 15 minutes and the maximum is eight hours. Browser automation uses the session's WebSocket endpoints.
Sources: docs.aws.amazon.com ↗
What survives a session
AWS AgentCore Browser: The Browser Tool documentation describes ephemeral sessions that reset after use. State that must outlive a session needs an explicit storage or authentication design rather than an assumption of permanent browser state.
Sources: docs.aws.amazon.com ↗
Website login
AWS AgentCore Browser: AWS credentials and IAM control access to the Browser Tool. Website login remains a separate concern: the identity used to authorize an AWS API call does not automatically sign the browser in to a third-party application.
Sources: docs.aws.amazon.com ↗
Where the code runs
AWS AgentCore Browser: The Browser Tool supplies the browser environment. An external process or another AWS execution service runs the application code that controls it. Identify that service and its runtime before comparing it with a deployed browser Function.
Sources: docs.aws.amazon.com ↗
Deployment ownership
AWS AgentCore Browser: Use an AWS-managed Browser Tool or configure a custom browser with recording, networking and an execution role. Keep the controller's deployment separate in the architecture and operational estimate.
Sources: docs.aws.amazon.com ↗
Capacity and limits
AWS AgentCore Browser: AgentCore Browser supports multiple simultaneous sessions. Review AWS quotas and the chosen tool/session configuration; the browser session's timeout and the controller's execution timeout are separate limits.
Sources: docs.aws.amazon.com ↗
Inspecting a run
AWS AgentCore Browser: Live View allows real-time browser interaction. Custom browsers support recording to your S3 bucket, with replay through the AWS Console. CloudWatch and CloudTrail provide additional operational visibility.
Sources: docs.aws.amazon.com ↗
Pricing model
AWS AgentCore Browser: A complete AWS workflow may include browser use, the controlling compute service, storage and other metered services. Price the selected architecture and region instead of treating a browser benchmark rate as the final invoice.
Sources: aws.amazon.com ↗
Where Notte is worth evaluating
AgentCore Browser's AWS integration can matter more than moving a browser endpoint. Retain AWS identity and observability requirements in the evaluation, and separately account for the code runner and website login before comparing Notte's integrated workflow.
Notte combines cloud browser sessions with deployed Python automations and website authentication tools. You can control the browser over CDP or use Notte's actions, then deploy repeated work as a Function.
Retaining AWS AgentCore Browser can be the right outcome when its documented model already fits the application. Compare Notte only against a concrete missing capability, operating responsibility or cost constraint.
Sources: docs.aws.amazon.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
Questions to settle before buying
The browser tool is not the entire AgentCore platform. Do not assign capabilities from unrelated AgentCore execution or identity products to a browser session without specifying the composition.
Ask for the exact session, state and execution contract of the proposed account. A published browser observation does not establish feature availability, supported websites or production access.
- Which workload must pass before purchase?
- Who owns the running code, stored browser state and website connection?
- Which browser and handler limits apply to the selected plan?
- What does the invoice include beyond browser usage?
- What would have to be rebuilt to leave this provider?