{"id":11774,"date":"2026-02-13T23:56:13","date_gmt":"2026-02-13T23:56:13","guid":{"rendered":"https:\/\/techtrendfeed.com\/?p=11774"},"modified":"2026-02-13T23:56:13","modified_gmt":"2026-02-13T23:56:13","slug":"customise-ai-agent-searching-with-proxies-profiles-and-extensions-in-amazon-bedrock-agentcore-browser","status":"publish","type":"post","link":"https:\/\/techtrendfeed.com\/?p=11774","title":{"rendered":"Customise AI agent searching with proxies, profiles, and extensions in Amazon Bedrock AgentCore Browser"},"content":{"rendered":"


\n<\/p>\n

\n

AI brokers that browse the online want greater than fundamental web page navigation. Our clients inform us they want brokers that preserve session state throughout interactions, route site visitors by way of company proxy infrastructure, and run with customized browser configurations. AgentCore Browser<\/a> supplies a safe, remoted browser surroundings in your brokers to work together with net purposes. Till now, in Agent Core Browser, every browser session began from a clean slate with default settings and direct web entry, limiting what brokers might accomplish in real-world enterprise environments.<\/p>\n

Immediately, we’re saying three new capabilities that deal with these necessities: proxy configuration<\/a>, browser profiles<\/a>, and browser extensions<\/a>. Collectively, these options provide you with fine-grained management over how your AI brokers work together with the online.<\/p>\n

These three capabilities provide you with management over how AgentCore Browser classes hook up with the web, what state they preserve, and the way they behave. Proxy configuration enables you to route browser site visitors by way of your individual proxy servers, offering IP stability and integration with company community infrastructure. Browser profiles persist cookies and native storage throughout classes, so brokers can resume authenticated workflows with out repeating login flows. Browser extensions load Chrome extensions into classes to customise browser conduct in your use case. This publish will stroll by way of every functionality with configuration examples and sensible use instances that will help you get began.<\/p>\n

How persistent browser profiles preserve AI Brokers operating easily<\/h2>\n

Prospects constructing brokers for e-commerce testing, authenticated workflows, and multi-step consumer journeys want browser classes that keep in mind state. With out persistent profiles, brokers are required to re-authenticate and rebuild context initially of each session, including latency and fragility to automated workflows. Browser profiles remedy this by saving and restoring cookies and native storage between classes, so an agent that logged right into a portal yesterday can choose up the place it left off as we speak.<\/p>\n

IP stability is one other frequent requirement. Healthcare and monetary portals validate classes primarily based on supply IP deal with, and rotating AWS IP addresses trigger frequent re-authentication cycles that break long-running workflows. Proxy assist enables you to route site visitors by way of servers with secure egress IPs, sustaining session continuity and assembly IP allowlisting necessities. Organizations that route site visitors by way of company proxies want to increase this follow to AI brokers for browser classes. Proxy configuration allows entry to inside webpages and sources that require proxy-based connectivity.<\/p>\n

Browser extensions permit customized configurations reminiscent of advert blocking, authentication helpers, or different browser-level customization. When mixed with proxy logging, these capabilities helps present entry management and audit proof that might\u00a0<\/span><\/span>compliance packages<\/span><\/span><\/a>\u00a0reminiscent of FedRAMP, HITRUST, and PCI<\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n

Characteristic 1: Proxy configuration<\/h2>\n

Browser\u00a0<\/span>now helps routing browser site visitors by way of your individual exterior proxy servers. If you create a browser session with proxy configuration, AgentCore configures the browser to route HTTP and HTTPS site visitors by way of your specified proxy servers.<\/p>\n

The way it works<\/h3>\n

You name StartBrowserSession<\/code> with a proxyConfiguration<\/code> specifying your proxy server. If utilizing authentication, AgentCore retrieves proxy credentials from AWS Secrets and techniques Supervisor. The browser session begins along with your proxy configuration utilized, and browser site visitors routes by way of your proxy server primarily based in your area routing guidelines.<\/p>\n

Getting began with proxies<\/h3>\n

Full these conditions<\/a> earlier than continuing.<\/p>\n

\n
import boto3 \nimport json \nconsumer = boto3.consumer('secretsmanager') \nconsumer.create_secret( \n    Identify=\"my-proxy-credentials\", \n    SecretString=json.dumps({ \n        'username': '', \n        'password': '' \n    }) \n) <\/your-password><\/your-username><\/code><\/pre>\n<\/p><\/div>\n
Step 2:<\/strong> Create a browser session with proxy configuration<\/span><\/span>\u00a0<\/span><\/p>\n
\n
session_client = boto3.consumer('bedrock-agentcore', region_name=\"\") \n \nresponse = session_client.start_browser_session( \n    browserIdentifier=\"aws.browser.v1\", \n    title=\"my-proxy-session\", \n    proxyConfiguration={ \n        \"proxies\": [{ \n            \"externalProxy\": { \n                \"server\": \"\", \n                \"port\": 8080, \n                \"credentials\": { \n                    \"basicAuth\": { \n                        \"secretArn\": \"arn:aws:secretsmanager:::secret:\" \n                    } \n                } \n            } \n        }] \n    } \n) \nprint(f\"Session ID: {response['sessionId']}\")<\/secret-name><\/account-id><\/region><\/your-proxy-hostname><\/region><\/code><\/pre>\n<\/p><\/div>\n
The credentials discipline is non-obligatory for proxies with out authentication.<\/p>\n
Area-based routing<\/h3>\n
Use domainPatterns<\/code> to route particular domains by way of designated proxies, and bypass.domainPatterns<\/code> for domains that ought to join instantly:<\/p>\n
\n
proxyConfiguration={ \n    \"proxies\": [ \n        { \n            \"externalProxy\": { \n                \"server\": \"corp-proxy.example.com\", \n                \"port\": 8080, \n                \"domainPatterns\": [\".company.com\", \".internal.corp\"] \n            } \n        }, \n        { \n            \"externalProxy\": { \n                \"server\": \"general-proxy.instance.com\", \n                \"port\": 8080 \n            } \n        } \n    ], \n    \"bypass\": { \n        \"domainPatterns\": [\".amazonaws.com\"] \n    } \n}<\/code><\/pre>\n<\/p><\/div>\n
With this configuration, requests to\u00a0<\/span><\/span><\/code>\u00a0and\u00a0<\/span><\/span>inside.corp<\/span><\/span><\/code>\u00a0<\/span>route by way of the company\u00a0<\/span>proxy,\u00a0<\/span>\u00a0requests<\/span>\u00a0to\u00a0<\/span><\/span>amazonaws.com<\/span><\/span><\/code>\u00a0<\/span>bypass all proxies<\/span>, and all the pieces else routes by way of the final proxy.<\/span>\u00a0Th<\/span>e<\/span>s<\/span>e fields<\/span>\u00a0<\/span>are<\/span>\u00a0simply an instance.\u00a0<\/span><\/span>Bypass domains<\/span><\/span>\u00a0can match\u00a0<\/span><\/span>bypass.domainPatterns<\/span><\/span><\/code>\u00a0to attach instantly and\u00a0<\/span><\/span>exterior\u00a0<\/span>proxy<\/span>\u00a0<\/span><\/span>could be a\u00a0<\/span>legitimate\u00a0<\/span>proxy\u2019s<\/span>\u00a0<\/span><\/span>domainPatterns<\/span><\/code>\u00a0<\/span><\/span>route by way of that proxy (first match wins primarily based on array order).<\/span><\/span>\u00a0<\/span><\/p>\n
Routing priority<\/h3>\n
When AgentCore Browser processes an outbound request, it walks by way of three tiers of routing guidelines to resolve the place to ship the site visitors. It first checks the bypass listing. If the vacation spot area matches a bypass.domainPatterns<\/code> entry, the request connects on to the web with out utilizing any proxy. If the area doesn’t match a bypass rule, AgentCore checks every proxy\u2019s domainPatterns<\/code> so as and routes the request by way of the primary proxy whose sample matches. If no proxy sample matches both, the request falls by way of to the default proxy, which is the proxy entry that has no domainPatterns<\/code> outlined.<\/p>\n
Check the brand new proxy characteristic with this code instance<\/a>.<\/p>\n
Characteristic 2: Browser profiles<\/h2>\n
Browser profiles allow you to persist and reuse session information throughout a number of browser classes, together with cookies and native storage. An agent that authenticates with an internet portal in a single session can restore that state in a later session with out logging in once more. That is helpful for authenticated workflows the place re-login provides latency, e-commerce testing the place procuring carts and type information must survive between classes, and multi-step consumer journeys that span a number of browser invocations.<\/p>\n
The profile lifecycle has 4 phases. You begin by calling create_browser_profile()<\/code> to create a named profile. On the finish of a session, you name save_browser_session_profile()<\/code> to seize the present cookies and native storage into that profile. If you begin a brand new session, you cross the profile identifier within the profileConfiguration<\/code> parameter of start_browser_session()<\/code>, which restores the saved state into the brand new browser. If you now not want the profile, you name delete_browser_profile()<\/code> to scrub it up.<\/p>\n
The next instance exhibits an agent that provides gadgets to a procuring cart in a single session and verifies they persist in a subsequent session.<\/p>\n
Full these conditions<\/a> earlier than continuing.<\/p>\n
\n
import boto3 \n\ncontrol_client = boto3.consumer('bedrock-agentcore-control', region_name=\"\") # substitute by your area \n\nsession_client = boto3.consumer('bedrock-agentcore', region_name=\"\") # substitute by your area  \n \n# Create a browser profile \nprofile = control_client.create_browser_profile(title=\"ecommerce_profile\") \nprofile_id = profile['profileId'] \n \n# Session 1: Add gadgets to cart \nsession1 = session_client.start_browser_session( \n    browserIdentifier=\u201daws.browser.v1\u201d, \n    title=\"shopping-session-1\" \n) \n# ... agent navigates and provides gadgets to cart ... \n \n# Save session state to profile \nsession_client.save_browser_session_profile( \n    sessionId=session1['sessionId'], \n    browserIdentifier=\u201daws.browser.v1\u201d, \n    profileIdentifier=profile_id \n) \nsession_client.stop_browser_session(sessionId=session1['sessionId'], browserIdentifier=\"aws.browser.v1\") \n \n# Session 2: Resume with saved profile \nsession2 = session_client.start_browser_session( \n    browserIdentifier=\u201daws.browser.v1\u201d, \n    title=\"shopping-session-2\", \n    profileConfiguration={\"profileIdentifier\": profile_id} \n) \n# Cart gadgets from Session 1 are actually accessible <\/region><\/region><\/code><\/pre>\n<\/p><\/div>\n
Check the brand new profile characteristic with this code instance<\/a>.<\/p>\n
Characteristic 3: Browser extensions<\/h2>\n
Browser extensions allow you to load Chrome extensions into AgentCore Browser classes to customise how the browser behaves. You bundle extensions as ZIP information, add them to Amazon Easy Storage Service<\/a><\/span> (Amazon S3), and reference them when beginning a browser session. This supplies entry to performance accessible by way of the Chrome extension API, from proxy routing and advert blocking to authentication helpers and content material modification. For instance, you’ll be able to inject authentication tokens for inside purposes, take away advertisements, and observe scripts that intervene with agent navigation, or modify web page content material to enhance how brokers work together with a web site.<\/p>\n
Your extension ought to observe the usual Chromium extension<\/a> format and cling to Chromium extension pointers.<\/p>\n
Full these conditions<\/a> earlier than continuing.<\/p>\n
    \n
  1. Add the extension to Amazon S3:\n
    \n
    # Add extension to S3 \n\nimport boto3 \ns3 = boto3.consumer('s3') \ns3.upload_file( \n    'my-extension.zip', \n    'amzn-s3-demo-bucket-extensions', \n    'extensions\/my-extension.zip' \n) <\/code><\/pre>\n<\/p><\/div>\n<\/li>\n
  2. Then, begin a session with the extension, pointing to the Amazon S3 bucket the place you\u2019ve uploaded the zip file:\n
    \n
    import boto3 \narea = \"\" # substitute by your area \nconsumer = boto3.consumer('bedrock-agentcore', region_name=area) \n\nresponse = consumer.start_browser_session( \n    browserIdentifier=\"aws.browser.v1\", \n    title=\"my-session-with-extensions\", \n    sessionTimeoutSeconds=1800, \n    viewPort={ \n        'peak': 1080, \n        'width': 1920 \n    }, \n    extensions=[ \n        { \n            \"location\": { \n                \"s3\": { \n                    \"bucket\": \"amzn-s3-demo-bucket-extensions\", \n                    \"prefix\": \"extensions\/my-extension.zip\" \n                } \n            } \n        }, \n        { \n            \"location\": { \n                \"s3\": { \n                    \"bucket\": \"amzn-s3-demo-bucket-extensions\", \n                    \"prefix\": \"extensions\/another-extension.zip\", \n                    \"versionId\": \"abc123\"  # Optional - for versioned S3 buckets \n                } \n            } \n        } \n    ] \n) \n \nprint(f\"Session ID: {response['sessionId']}\") \nprint(f\"Standing: {response['status']}\") \nprint(f\"Automation Stream: {response['streams']['automationStream']['streamEndpoint']}\") <\/region><\/code><\/pre>\n<\/p><\/div>\n<\/li>\n<\/ol>\n
    Check the brand new extensions characteristic with this code instance<\/a>.<\/p>\n
    Conclusion<\/h2>\n
    Proxy configuration, browser profiles, and browser extensions give AgentCore Browser the proxy routing, session persistence, and extensibility controls that clients must deploy AI brokers that browse the online in manufacturing. You may route site visitors by way of your company proxy infrastructure, preserve session continuity throughout interactions, and customise browser conduct with extensions, all whereas preserving credentials safe in AWS Secrets and techniques Supervisor. Prospects can carry e-commerce context and data amongst classes, create your individual extension and check it in a safe surroundings earlier than launch, and, additionally, have browser connecting into your community by way of proxies.<\/span>\u00a0<\/span><\/p>\n
    To get began, see the tutorials within the\u00a0<\/span>Amazon Bedrock AgentCore\u00a0samples<\/span><\/a>\u00a0repository and the\u00a0Amazon Bedrock\u00a0AgentCore\u00a0Browser\u00a0<\/span>documentation<\/span><\/a>.\u00a0\u00a0<\/span>For extra details about pricing, go to\u00a0<\/span>Amazon Bedrock AgentCore Pricing<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n\n
    Concerning the Authors<\/h2>\n