Customise AI agent shopping with proxies, profiles, and extensions in Amazon Bedrock AgentCore Browser

AI brokers that browse the net want greater than fundamental web page navigation. Our clients inform us they want brokers that keep session state throughout interactions, route visitors by way of company proxy infrastructure, and run with customized browser configurations. AgentCore Browser offers a safe, remoted browser atmosphere in your brokers to work together with internet 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 may accomplish in real-world enterprise environments.

Right this moment, we’re asserting three new capabilities that tackle these necessities: proxy configuration, browser profiles, and browser extensions. Collectively, these options provide you with fine-grained management over how your AI brokers work together with the net.

These three capabilities provide you with management over how AgentCore Browser periods hook up with the web, what state they maintain, and the way they behave. Proxy configuration enables you to route browser 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 periods, so brokers can resume authenticated workflows with out repeating login flows. Browser extensions load Chrome extensions into periods 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 can assist you get began.

How persistent browser profiles hold AI Brokers working easily

Prospects constructing brokers for e-commerce testing, authenticated workflows, and multi-step consumer journeys want browser periods that bear in mind state. With out persistent profiles, brokers are required to re-authenticate and rebuild context in the beginning of each session, including latency and fragility to automated workflows. Browser profiles remedy this by saving and restoring cookies and native storage between periods, so an agent that logged right into a portal yesterday can decide up the place it left off right this moment.

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

Browser extensions enable customized configurations similar to 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 compliance applications similar to FedRAMP, HITRUST, and PCI. 

Function 1: Proxy configuration

Browser now helps routing browser visitors by way of your individual exterior proxy servers. Once you create a browser session with proxy configuration, AgentCore configures the browser to route HTTP and HTTPS visitors by way of your specified proxy servers.

The way it works

You name StartBrowserSession with a proxyConfiguration 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 visitors routes by way of your proxy server primarily based in your area routing guidelines.

Getting began with proxies

Full these stipulations earlier than continuing.

import boto3 
import json 
shopper = boto3.shopper('secretsmanager') 
shopper.create_secret( 
    Identify="my-proxy-credentials", 
    SecretString=json.dumps({ 
        'username': '', 
        'password': '' 
    }) 
) 

Step 2: Create a browser session with proxy configuration 

session_client = boto3.shopper('bedrock-agentcore', region_name="") 
 
response = session_client.start_browser_session( 
    browserIdentifier="aws.browser.v1", 
    identify="my-proxy-session", 
    proxyConfiguration={ 
        "proxies": [{ 
            "externalProxy": { 
                "server": "", 
                "port": 8080, 
                "credentials": { 
                    "basicAuth": { 
                        "secretArn": "arn:aws:secretsmanager:::secret:" 
                    } 
                } 
            } 
        }] 
    } 
) 
print(f"Session ID: {response['sessionId']}")

The credentials area is optionally available for proxies with out authentication.

Area-based routing

Use domainPatterns to route particular domains by way of designated proxies, and bypass.domainPatterns for domains that ought to join straight:

proxyConfiguration={ 
    "proxies": [ 
        { 
            "externalProxy": { 
                "server": "corp-proxy.example.com", 
                "port": 8080, 
                "domainPatterns": [".company.com", ".internal.corp"] 
            } 
        }, 
        { 
            "externalProxy": { 
                "server": "general-proxy.instance.com", 
                "port": 8080 
            } 
        } 
    ], 
    "bypass": { 
        "domainPatterns": [".amazonaws.com"] 
    } 
}

With this configuration, requests to  and inside.corp route by way of the company proxy,  requests to amazonaws.com bypass all proxies, and every little thing else routes by way of the final proxy. These fields are simply an instance. Bypass domains can match bypass.domainPatterns to attach straight and exterior proxy generally is a legitimate proxy’s domainPatterns route by way of that proxy (first match wins primarily based on array order). 

Routing priority

When AgentCore Browser processes an outbound request, it walks by way of three tiers of routing guidelines to determine the place to ship the visitors. It first checks the bypass listing. If the vacation spot area matches a bypass.domainPatterns 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’s domainPatterns 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 outlined.

Take a look at the brand new proxy function with this code instance.

Function 2: Browser profiles

Browser profiles allow you to persist and reuse session knowledge throughout a number of browser periods, 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 knowledge have to survive between periods, and multi-step consumer journeys that span a number of browser invocations.

The profile lifecycle has 4 levels. You begin by calling create_browser_profile() to create a named profile. On the finish of a session, you name save_browser_session_profile() to seize the present cookies and native storage into that profile. Once you begin a brand new session, you move the profile identifier within the profileConfiguration parameter of start_browser_session(), which restores the saved state into the brand new browser. Once you not want the profile, you name delete_browser_profile() to wash it up.

The next instance reveals an agent that provides objects to a procuring cart in a single session and verifies they persist in a subsequent session.

Full these stipulations earlier than continuing.

import boto3 

control_client = boto3.shopper('bedrock-agentcore-control', region_name="") # exchange by your area 

session_client = boto3.shopper('bedrock-agentcore', region_name="") # exchange by your area  
 
# Create a browser profile 
profile = control_client.create_browser_profile(identify="ecommerce_profile") 
profile_id = profile['profileId'] 
 
# Session 1: Add objects to cart 
session1 = session_client.start_browser_session( 
    browserIdentifier=”aws.browser.v1”, 
    identify="shopping-session-1" 
) 
# ... agent navigates and provides objects to cart ... 
 
# Save session state to profile 
session_client.save_browser_session_profile( 
    sessionId=session1['sessionId'], 
    browserIdentifier=”aws.browser.v1”, 
    profileIdentifier=profile_id 
) 
session_client.stop_browser_session(sessionId=session1['sessionId'], browserIdentifier="aws.browser.v1") 
 
# Session 2: Resume with saved profile 
session2 = session_client.start_browser_session( 
    browserIdentifier=”aws.browser.v1”, 
    identify="shopping-session-2", 
    profileConfiguration={"profileIdentifier": profile_id} 
) 
# Cart objects from Session 1 are actually obtainable 

Take a look at the brand new profile function with this code instance.

Function 3: Browser extensions

Browser extensions allow you to load Chrome extensions into AgentCore Browser periods to customise how the browser behaves. You bundle extensions as ZIP recordsdata, add them to Amazon Easy Storage Service (Amazon S3), and reference them when beginning a browser session. This offers entry to performance obtainable by way of the Chrome extension API, from proxy routing and advert blocking to authentication helpers and content material modification. For instance, you may inject authentication tokens for inside purposes, take away adverts, and observe scripts that intrude with agent navigation, or modify web page content material to enhance how brokers work together with a website.

Your extension ought to observe the usual Chromium extension format and cling to Chromium extension pointers.

Full these stipulations earlier than continuing.

1. Add the extension to Amazon S3:

   # Add extension to S3 
   
   import boto3 
   s3 = boto3.shopper('s3') 
   s3.upload_file( 
       'my-extension.zip', 
       'amzn-s3-demo-bucket-extensions', 
       'extensions/my-extension.zip' 
   ) 

2. Then, begin a session with the extension, pointing to the Amazon S3 bucket the place you’ve uploaded the zip file:

   import boto3 
   area = "" # exchange by your area 
   shopper = boto3.shopper('bedrock-agentcore', region_name=area) 
   
   response = shopper.start_browser_session( 
       browserIdentifier="aws.browser.v1", 
       identify="my-session-with-extensions", 
       sessionTimeoutSeconds=1800, 
       viewPort={ 
           'peak': 1080, 
           'width': 1920 
       }, 
       extensions=[ 
           { 
               "location": { 
                   "s3": { 
                       "bucket": "amzn-s3-demo-bucket-extensions", 
                       "prefix": "extensions/my-extension.zip" 
                   } 
               } 
           }, 
           { 
               "location": { 
                   "s3": { 
                       "bucket": "amzn-s3-demo-bucket-extensions", 
                       "prefix": "extensions/another-extension.zip", 
                       "versionId": "abc123"  # Optional - for versioned S3 buckets 
                   } 
               } 
           } 
       ] 
   ) 
    
   print(f"Session ID: {response['sessionId']}") 
   print(f"Standing: {response['status']}") 
   print(f"Automation Stream: {response['streams']['automationStream']['streamEndpoint']}") 

Take a look at the brand new extensions function with this code instance.

Conclusion

Proxy configuration, browser profiles, and browser extensions give AgentCore Browser the proxy routing, session persistence, and extensibility controls that clients have to deploy AI brokers that browse the net in manufacturing. You’ll be able to route visitors by way of your company proxy infrastructure, keep 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 periods, create your individual extension and take a look at it in a safe atmosphere earlier than launch, and, additionally, have browser connecting into your community by way of proxies. 

To get began, see the tutorials within the Amazon Bedrock AgentCore samples repository and the Amazon Bedrock AgentCore Browser documentation.  For extra details about pricing, go to Amazon Bedrock AgentCore Pricing. 

In regards to the Authors