Amazon Bedrock AgentCore Gateway websearch samples and usecases

[nagagaddamu]

Amazon Bedrock AgentCore Samples Pull Request

Important

1. We strictly follow a issue-first approach, please first open an issue relating to this Pull Request.
2. Once this Pull Request is ready for review please attach review ready label to it. Only PRs with review ready will be reviewed.

Issue number: This is a new Agent Core web search feature - #1646

Concise description of the PR

Adds AgentCore Web Search Tool samples and a deep-research-agent use case. Customers need end-to-end examples showing how to set up the Web Search connector via AgentCore Gateway, integrate it with Strands Agents and LangChain, and apply multi-turn research patterns. The feature samples cover the full lifecycle — Gateway provisioning, raw MCP verification, agent integration, and resource cleanup. The Deep Research Agent demonstrates a multi-turn iterative pattern (Plan → Search → Reflect → Synthesize).

User experience

No samples existed for the AgentCore Web Search Tool. Customers had no reference on how to provision the Gateway with a web-search connector, authenticate via Cognito, or integrate the tool with popular agentic frameworks.

AFTER:
Customers get:
1/ Feature samples (01-features/03-connect-your-agent-to-anything/03-web-search/) — Gateway setup script, raw MCP verification, Strands agent demo, LangChain agent demo, and cleanup script with shared utilities.
2/ Use case (02-use-cases/deep-research-agent/) — A deep-research agent that auto-provisions its own Gateway and performs multi-turn iterative web research with cited sources.
Each sample includes a README documenting introduction, architecture, prerequisites, usage, sample prompts, and cleanup steps.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have reviewed the contributing guidelines
• Add your name to CONTRIBUTORS.md
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [] Are you uploading a dataset?
• Have you documented Introduction, Architecture Diagram, Prerequisites, Usage, Sample Prompts, and Clean Up steps in your example README?
• I agree to resolve any issues created for this example in the future.
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[vedashreevinay]

approved.

[github-actions]

Latest scan for commit: 442ccac | Updated: 2026-06-23 17:51:35 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-06-23T17:51:18+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	2	0	1.0s	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	7.0s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	4ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	5.7s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	1.0s	0	PASSED	MED (g)
grype	0	0	0	0	0	0	47.5s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	184ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	2.2s	0	PASSED	MED (g)

[nagagaddamu]

@BharathiSrini Resolved issues with naming convention, updated Web Search Tool architecture , and supported region note