AWS opens AgentCore web search to direct API calls, with IAM and private networking

AWS has introduced a direct Web Search API for Amazon Bedrock AgentCore, letting developers fetch current web results without first setting up an AgentCore Gateway. The useful change is more control over how search fits into an application, including private-network access and filters for domains and publication dates.

AWS AI Watch analysis

What happened

The API returns ranked results with text extracts and, when available, page titles, URLs and publication times. Developers can call it through AWS SDKs or the command line, using their standard AWS credentials. AWS says no API key or search resource needs to be created.

The AWS announcement and integration guide says each request can return up to 25 results. Developers can include or exclude domains and set inclusive publication-date limits. Calls use AWS Signature Version 4, and the API checks IAM permissions.

Why it matters

The direct route is aimed at custom agent loops, existing applications and non-agent tools such as dashboards or monitoring pipelines. Teams can handle retries, caching and error handling themselves rather than routing those calls through a gateway. AWS says searches use an Amazon-operated index and queries are served within AWS, not sent to a third-party search engine.

There are also enterprise controls: calls can use PrivateLink, and CloudTrail can record API requests as data events. Those events are not logged by default, so teams need to configure them. A useful detail for anyone whose audit trail currently consists of crossed fingers.

Our read

This is a meaningful infrastructure option for teams that want current search results without adopting the full Gateway setup. It returns evidence for an application to process, not a finished, source-cited answer. That distinction leaves developers with more control, and more responsibility for checking what their systems do with the results.

What to watch

• Whether AWS adds regional availability or changes the default account quota of 10 requests per second per Region.
• How developers use domain and date filters to constrain searches.
• Whether AWS’s usage terms and citation requirements fit teams’ intended applications.

Discussion spark: For AI tools using live web results, would you rather keep retrieval and interpretation under your own control, or use a managed service that handles more of the pipeline?

not affiliated with or endorsed by Amazon Web Services (AWS)