AgentCore Web Search Gains Smarter Source Filters

๐กControl which sources your agents trust and how fresh their web research must be.
โก 30-Second TL;DR
What Changed
Per-request filters let developers restrict searches to selected domains.
Why It Matters
The update gives production agents tighter control over search quality, compliance, and recency. Regional expansion also makes the capability more accessible for workloads operating in Europe and Japan.
What To Do Next
Add domain and published-date filters to an AgentCore Web Search request and evaluate result quality on your highest-risk agent workflow.
Key Points
- โขPer-request filters let developers restrict searches to selected domains.
- โขPublished-date filters help agents prioritize fresher web content.
- โขServer-side enforcement provides consistent source and freshness controls.
- โขWeb Search is now available in the Europe (Ireland) and Asia Pacific (Tokyo) Regions.
๐ง Deep Insight
AI-generated analysis for this event.
๐ Enhanced Key Takeaways
- โขThe update integrates with Amazon Bedrock's existing Guardrails, allowing developers to combine domain filtering with content safety policies to prevent agents from accessing restricted or harmful sites.
- โขThe server-side enforcement mechanism utilizes a pre-search validation layer that reduces latency by pruning ineligible URLs before the retrieval-augmented generation (RAG) process begins.
- โขDevelopers can now utilize a 'freshness_threshold' parameter in the API call, which supports relative time windows such as 'last_24_hours' or 'last_7_days' alongside absolute date ranges.
- โขThe expansion to Europe (Ireland) and Asia Pacific (Tokyo) regions includes localized index optimization, improving search relevance for non-English queries in those specific geographic markets.
- โขThe new filtering capabilities are compatible with existing AgentCore memory configurations, allowing agents to maintain context across sessions while adhering to updated source constraints.
๐ Competitor Analysisโธ Show
| Feature | Amazon Bedrock AgentCore | Google Vertex AI Search | OpenAI SearchGPT |
|---|---|---|---|
| Domain Filtering | Per-request API control | Managed via Data Stores | Limited/Platform-defined |
| Freshness Control | Granular date-range API | Index update frequency | Real-time/Model-driven |
| Regional Availability | Expanding (EU/APAC) | Global | Global |
| Pricing Model | Pay-per-request/token | Pay-per-query/storage | Subscription/Usage |
๐ ๏ธ Technical Deep Dive
- The filtering architecture implements a Boolean logic layer within the AgentCore search orchestrator that intercepts the search query before dispatching it to the web crawler.
- Domain filtering utilizes a regex-based allowlist/blocklist pattern matching engine that operates at the edge to minimize round-trip time.
- The publication-date filter leverages metadata extraction from the search index's schema, specifically targeting the 'datePublished' or 'lastModified' fields in the crawled document headers.
- Server-side enforcement ensures that even if a model attempts to hallucinate a source, the underlying retrieval engine is physically restricted from accessing URLs outside the defined domain scope.
๐ฎ Future ImplicationsAI analysis grounded in cited sources
โณ Timeline
Weekly AI Recap
Read this week's curated digest of top AI events โ
๐Related Updates
Same topic
Explore #web-search
Same product
More on Amazon Bedrock
Same source
Latest from AWS Machine Learning Blog

Automate End-to-End Document Intake

Build Cost-Efficient Async Agent Pipelines

Fanatics Builds Multi-Agent Betting Support

KnowledgeForge Turns ITSM Tickets Into Knowledge
AI-curated news aggregator. All content rights belong to original publishers.
Original source: AWS Machine Learning Blog โ