AWS Adds Runtime Domain and Date Filters to AgentCore Web Search
Amazon Bedrock AgentCore Web Search now supports per-request domain allow/deny lists and publication-date filtering, giving agents tighter source and freshness controls inside AWS infrastructure.
What AWS released
On August 19, 2026, AWS announced runtime domain and published-date filtering for Web Search on Amazon Bedrock AgentCore. The features ship in web-search connector version 1.2.0 and add per-request controls over which web sources an agent may use and how recent returned content must be.
Domain controls
Developers can provide an include list or exclude list on each tool invocation. AWS says each list supports up to 100 domains independently. This allows an organization to combine administrator-level source policies with request-specific controls for regulated, tenant-specific or high-trust search workflows.
Publication-date filtering
The connector also accepts inclusive ISO-8601 UTC start and end bounds for publication dates. An agent can therefore restrict results to a requested time window, such as the last day or a known regulatory period, instead of relying only on semantic relevance.
Infrastructure and availability
Web Search is delivered through AgentCore Gateway and is compatible with MCP-based tool workflows. AWS says search queries remain within AWS infrastructure under its zero-data-egress architecture. Runtime domain and date filtering is available in US East (N. Virginia), Europe (Ireland) and Asia Pacific (Tokyo) for AgentCore Web Search.
Why it matters
Agentic search can fail even when retrieval quality is strong if the system uses stale or unapproved sources. Moving freshness and domain constraints into the managed search layer gives developers deterministic controls that can be audited independently of the model's own reasoning. The change is backward compatible for existing calls that omit the new filter object.
This article is built from the source material below. Open the originals for full context and the latest updates.