AWS explains authenticated web search for Claude Desktop through AgentCore
The short version
AWS published a tutorial connecting Claude Desktop configured for Amazon Bedrock to AgentCore Gateway’s MCP web search. The example combines IAM Identity Center, Cognito and OAuth authentication with AWS-managed search.
What changed
The article provides an integration recipe and identity flow rather than announcing a new Claude model or a general service launch.
What it means for you
Teams can evaluate how to add search to a Bedrock-backed desktop workflow while keeping access control explicit.
The example federates IAM Identity Center through SAML to Amazon Cognito, uses an OAuth 2.0 authorization-code flow and has AgentCore Gateway validate JWTs. Claude Desktop then accesses web search as an MCP tool.
AWS describes a managed search index that does not require third-party search API keys and keeps query traffic within AWS. At publication, the guide lists us-east-1, eu-west-1 and ap-northeast-1. Region availability and organizational permissions should be checked before reproducing the setup.
The recipe assumes administrative access to an AWS organization and a Claude Desktop configuration using Bedrock. Its practical value is the documented integration, not a claim that every Claude configuration lacks search. The publication timestamp comes from the official AWS blog RSS entry.
Fact check
- VerifiedThe tutorial integrates Bedrock-configured Claude Desktop with AgentCore Gateway MCP web search.Evidence
- VerifiedAuthentication combines IAM Identity Center SAML federation to Cognito, OAuth 2.0 authorization code and Gateway JWT validation.Evidence
- VerifiedAWS describes managed search without third-party API keys, query traffic in AWS, regions us-east-1/eu-west-1/ap-northeast-1 and AWS organization admin and Bedrock Desktop prerequisites.Evidence
Coverage timeline
- Primary sourceAWSAdd secure Web Search to Claude Desktop with Amazon Bedrock AgentCore
- Primary sourceAWSAWS official RSS publication timestamp