Where is Web Search on Amazon Bedrock AgentCore available?

It is currently available in the US East (N. Virginia) Region (us-east-1), Europe (Ireland) Region (eu-west-1), and Asia Pacific (Tokyo) Region (ap-northeast-1). The gateway must be created in one of these Regions.

Do I need external API keys or a third-party identity provider?

No. All query traffic stays within AWS infrastructure, with no external API keys to manage, and no separate credentials or third-party identity providers are required. The authentication chain stays within AWS.

Can I use a different identity provider than AWS IAM Identity Center?

Yes. AWS says the same pattern works with any SAML or OIDC-compatible identity provider, which you substitute by configuring it as a federation source in Amazon Cognito.

Large Language ModelsAI Business & IndustryAmazon AI Blog5m agoOct 3, 2026, 01:00 JST

AWS ties Web Search to Claude Desktop via AgentCore

Send on LINE

3 Key Points

What happened
AWS published a step-by-step guide to connect Claude Desktop on Amazon Bedrock to Web Search through AgentCore Gateway, securing it with JWT-based authentication that uses AWS IAM Identity Center and Amazon Cognito.
Why it matters
This closes Claude Desktop's knowledge cutoff gap, so enterprise users can pull current information such as recent documentation updates, live pricing, or weather while authentication stays inside the AWS boundary they already govern.
What to watch
The setup depends on having IAM Identity Center preconfigured and on creating the gateway in a supported Region, and AWS notes the same pattern works with any SAML or OIDC-compatible identity provider.

WHO IT HITSEnterprise IT and platform teams running Claude Desktop on Amazon Bedrock who need current web results without standing up separate credentials or third-party identity providers are the ones who would operationalize this setup.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Get news like this every morning, free

Context & Analysis

The starting point for this walkthrough is a familiar limitation: Claude Desktop on Amazon Bedrock can only answer from the model's training knowledge cutoff, so questions about recent documentation updates, live pricing, or weather cannot be retrieved on its own. AWS's post presents Amazon Bedrock AgentCore as the layer that closes that gap, and AgentCore Gateway as the specific component you wire into Claude Desktop.

The design choices matter for organizations already standardized on AWS. The guide uses AWS IAM Identity Center as the authentication source and Amazon Cognito as a federation layer with the OAuth 2.0 authorization code grant flow, so the identity path matches governance many enterprises already have in place rather than adding a separate identity system. AWS also stresses that the Web Search capability is fully managed and Model Context Protocol (MCP)-compatible, with its Amazon web index spanning tens of billions of documents, and that queries stay inside the customer's boundary.

The practical constraint is geographic: Web Search on Amazon Bedrock AgentCore is currently available in the US East (N. Virginia), Europe (Ireland), and Asia Pacific (Tokyo) Regions, so the gateway has to live in one of those. For teams evaluating this, the outcome likely hinges on whether their existing identity setup and Region choice line up with those prerequisites, and on whether the promise of no external API keys and no queries leaving the boundary is worth the configuration steps.

FAQ

Where is Web Search on Amazon Bedrock AgentCore available?: It is currently available in the US East (N. Virginia) Region (us-east-1), Europe (Ireland) Region (eu-west-1), and Asia Pacific (Tokyo) Region (ap-northeast-1). The gateway must be created in one of these Regions.
Do I need external API keys or a third-party identity provider?: No. All query traffic stays within AWS infrastructure, with no external API keys to manage, and no separate credentials or third-party identity providers are required. The authentication chain stays within AWS.
Can I use a different identity provider than AWS IAM Identity Center?: Yes. AWS says the same pattern works with any SAML or OIDC-compatible identity provider, which you substitute by configuring it as a federation source in Amazon Cognito.

Amazon AI BlogRead Original Article

Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Get it free

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.