From 7744b9100ef68f43ab87ca8eb5b1b8d8b117ddc3 Mon Sep 17 00:00:00 2001 From: mateo-berri <277851410+mateo-berri@users.noreply.github.com> Date: Wed, 19 Aug 2026 15:14:20 -0700 Subject: [PATCH] docs(search): stop advertising yaml litellm_params knobs the search router drops --- .../agentcore_websearch_config.yaml | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/litellm/proxy/example_config_yaml/agentcore_websearch_config.yaml b/litellm/proxy/example_config_yaml/agentcore_websearch_config.yaml index bc29794e2a3..12402095c4d 100644 --- a/litellm/proxy/example_config_yaml/agentcore_websearch_config.yaml +++ b/litellm/proxy/example_config_yaml/agentcore_websearch_config.yaml @@ -18,16 +18,17 @@ search_tools: # The gateway exposes the connector as "___WebSearch". # Default is "web-search-tool___WebSearch", matching the target name used - # in the AWS docs' boto3/CLI setup examples. Set this ONLY if your target - # was created with a different name (misconfiguration surfaces as an MCP - # "tool not found" error): - # tool_name: MyWebSearchTarget___WebSearch + # in the AWS docs' boto3/CLI setup examples. If your target was created + # with a different name (misconfiguration surfaces as an MCP "tool not + # found" error), set the AGENTCORE_SEARCH_TOOL_NAME env var or pass + # tool_name in the request body. The search router forwards only + # search_provider / api_key / api_base from this litellm_params block, + # so a tool_name set here would be silently ignored. - # AWS_IAM gateway (default): SigV4-signed. Omit keys to use the standard - # AWS credential chain (env / profile / IRSA / instance role), or set them - # explicitly: - # aws_access_key_id: os.environ/AWS_ACCESS_KEY_ID - # aws_secret_access_key: os.environ/AWS_SECRET_ACCESS_KEY + # AWS_IAM gateway (default): SigV4-signed using the standard AWS + # credential chain (env / profile / IRSA / instance role). Explicit + # aws_access_key_id / aws_secret_access_key set here would be silently + # ignored for the same reason; pass them per request instead. # CUSTOM_JWT gateway alternative — OAuth2 bearer token instead of SigV4: # api_key: os.environ/AGENTCORE_GATEWAY_TOKEN