AgentCore#

AWS Bedrock AgentCore provides cloud browser sessions with SigV4 authentication. Use it when running agent-browser in AWS environments or when you need managed cloud browsers backed by AWS infrastructure.

Setup#

Credentials are automatically resolved from:

  1. Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)
  2. AWS CLI (aws configure export-credentials) which supports SSO, profiles, IAM roles, etc.
agent-browser -p agentcore open https://example.com

Or use environment variables for CI/scripts:

export AGENT_BROWSER_PROVIDER=agentcore
agent-browser open https://example.com

The -p flag takes precedence over AGENT_BROWSER_PROVIDER.

Configuration#

VariableDescriptionDefault
AGENTCORE_REGIONAWS region for the AgentCore endpointus-east-1
AGENTCORE_BROWSER_IDBrowser identifieraws.browser.v1
AGENTCORE_PROFILE_IDBrowser profile for persistent state (cookies, localStorage)(none)
AGENTCORE_SESSION_TIMEOUTSession timeout in seconds3600
AWS_PROFILEAWS CLI profile for credential resolutiondefault
AWS_ACCESS_KEY_IDAWS access key (checked before AWS CLI fallback)(none)
AWS_SECRET_ACCESS_KEYAWS secret key(none)
AWS_SESSION_TOKENTemporary session token (for STS/SSO credentials)(none)

Browser Profiles#

Use AGENTCORE_PROFILE_ID to persist browser state (cookies, localStorage) across sessions:

AGENTCORE_PROFILE_ID=my-profile agent-browser -p agentcore open https://example.com

When a profile is set, AgentCore stores and restores browser state automatically between sessions.

Live View#

When a session starts, AgentCore prints a Live View URL to stderr:

Session: abc123-def456
Live View: https://us-east-1.console.aws.amazon.com/bedrock-agentcore/browser/aws.browser.v1/session/abc123-def456#

Open this URL in your browser to watch the agent session in real time from the AWS Console.

Credential Resolution#

AgentCore uses lightweight manual SigV4 signing (no AWS SDK dependency). Credentials are resolved in order:

  1. Environment variables (AWS_ACCESS_KEY_ID + AWS_SECRET_ACCESS_KEY, optionally AWS_SESSION_TOKEN)
  2. AWS CLI (aws configure export-credentials --format env), which supports SSO, IAM roles, credential files, and profiles

If using SSO, run aws sso login before launching agent-browser. Set AWS_PROFILE to select a specific named profile.

Example#

# Basic usage (credentials auto-resolved via AWS CLI)
agent-browser -p agentcore open https://example.com

# With a browser profile for persistent login state
AGENTCORE_PROFILE_ID=my-profile agent-browser -p agentcore open https://x.com/home

# With explicit region
AGENTCORE_REGION=eu-west-1 agent-browser -p agentcore open https://example.com

# With SSO profile
AWS_PROFILE=my-sso-profile agent-browser -p agentcore open https://example.com

When enabled, agent-browser connects to an AgentCore cloud browser session instead of launching a local browser. All commands work identically.