AWS Tightens Source Control for AgentCore Web Search
AWS says Web Search on Amazon Bedrock AgentCore now supports runtime domain and published-date filtering. The release gives developers per-call control over which web domains an agent may search and how recent returned sources must be. AWS frames the change as a server-side governance feature for grounded AI agents, not as a client-side filtering workaround. The same update also expands Web Search availability to AWS Regions in Ireland and Tokyo.Per-request filters move source control into the API call
The core change is that Web Search on Amazon Bedrock AgentCore can now accept domain and publication-date constraints at runtime. AWS says the capability is included in web-search connector version 1.2.0 and is applied through the filters object in the Web Search tool input schema.For domain control, a caller can pass either an include list or an exclude list on each tools/call invocation. Each list supports up to 100 domains, counted independently. That gives an agent workflow a way to narrow a search to approved sources for one request, then use a different approved scope for another request without creating a separate connector target for every task.
The practical implication is a cleaner boundary between a model's language instructions and the search system's enforceable behavior. A prompt can ask an agent to prefer official sources, but an API-level domain filter can prevent unapproved domains from entering the returned search results in the first place.
Admin policies still define the outer boundary
AWS says runtime filters can narrow, but cannot expand, the scope set by an administrator. This is the main governance safeguard in the release: per-call flexibility is available only inside the domain boundaries already configured at the connector resource level.The blog describes the composition rules directly. Admin and runtime include lists merge by intersection, so only domains present in both lists remain searchable. Admin and runtime exclude lists merge by union, so a domain blocked at either level stays blocked. In AWS's example, a runtime request that includes a domain outside the admin allowlist is silently narrowed rather than granted broader access.
That model matters for enterprise agent deployments because developers can adapt source scope to the task while compliance teams retain a hard ceiling. A customer-support agent, legal research assistant or financial-services agent can receive task-specific limits without weakening the administrator's baseline policy.
Freshness filters trade recall for verifiable relevance
The second new control is published-date filtering. AWS says developers can restrict results to content published within a specific date range using ISO-8601 UTC bounds, with the filter applied per request and omitted when existing behavior is preferred.AWS also states that when filters are active, Web Search prioritizes precision over recall. If a domain filter is active, results without a recognizable domain are excluded. If a date filter is active, results without a recognized publication date are excluded. That means a filtered request may return fewer results, but AWS says the returned results satisfy the specified criteria.
This is especially relevant for agent answers that depend on current information. A product-information agent answering a question about availability should not ground a response in years-old inventory data. A market-intelligence or investor-relations workflow may also need a defined time window, though any financial use remains a controls and information-quality issue rather than investment advice.
Regional expansion adds Ireland and Tokyo endpoints
Alongside runtime filtering, AWS says Web Search on Amazon Bedrock AgentCore is now available in Europe (Ireland), identified as eu-west-1, and Asia Pacific (Tokyo), identified as ap-northeast-1. The feature is also available in US East (N. Virginia), us-east-1.The regional expansion gives customers in Europe and Asia Pacific a closer endpoint for invoking Web Search from workloads in those regions. AWS says this can reduce latency and provide an EU-based entry point for organizations with data proximity requirements.
AWS also says AgentCore uses a zero-egress architecture for Web Search, with search queries remaining within AWS infrastructure and not being sent to a third-party search engine or routed outside AWS. For regulated organizations, the immediate implication is a narrower external dependency surface for review when building grounded AI agents.
Developer impact centers on managed enforcement
The release is aimed at developers building agents that need grounded web information but cannot rely only on model behavior to choose sources. AWS positions Web Search as delivered through AgentCore Gateway, a managed endpoint compatible with the Model Context Protocol for connecting agents to tools.The announcement says the new fields are additive, the filters object is optional and connector version 1.2.0 is a minor release with no breaking changes. Existing API calls without filters continue to work as before. AWS also says the capability is supported across AWS SDKs, the AWS Command Line Interface, the AgentCore CLI and the AWS Console for AgentCore Web Search target configuration.
For builders, the difference is operational. Without server-side filtering, an application may need extra orchestration, post-processing or trust in prompt instructions to keep citations within policy. AWS says these controls are enforced server-side, with no client-side filtering loop, no post-processing and no additional roundtrips.
Conclusion
Amazon Bedrock AgentCore's new Web Search filters are a governance feature for agentic applications that need both live information and tighter source controls. Domain filters address which sources can be consulted, while published-date filters address whether the information is recent enough for the task.The most important design choice is that runtime filters cannot override administrator policy. That keeps enterprise controls intact while allowing individual API calls to narrow source scope dynamically. With Ireland and Tokyo added to availability, AWS is also making the feature more usable for regional workloads that care about latency and data proximity.
Sources
Editorial Team - CoinBotLab
