AWS bedrock-agentcore documentation change
Summary
Removed references to built-in connectors and deleted the Integrations/Connectors section
Security assessment
The changes remove documentation about deprecated/non-existent features without any security context. No security vulnerabilities, fixes, or security features are mentioned.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-core-concepts.md b/bedrock-agentcore/latest/devguide/gateway-core-concepts.md index 4c93e8381..24776ac9c 100644 --- a//bedrock-agentcore/latest/devguide/gateway-core-concepts.md +++ b//bedrock-agentcore/latest/devguide/gateway-core-concepts.md @@ -42 +42 @@ Gateway supports two categories of targets: -MCP targets operate in aggregation mode. The gateway combines the capabilities of all MCP targets into a single unified virtual MCP server. Clients see one consolidated `tools/list` response that includes tools from all attached MCP targets. MCP targets support capability synchronization, semantic tool search, and three-legged OAuth (3LO) at the target level. MCP target types include Lambda functions, API Gateway REST APIs, OpenAPI specifications, Smithy models, MCP servers, built-in integration provider templates and built-in connectors to tools. +MCP targets operate in aggregation mode. The gateway combines the capabilities of all MCP targets into a single unified virtual MCP server. Clients see one consolidated `tools/list` response that includes tools from all attached MCP targets. MCP targets support capability synchronization, semantic tool search, and three-legged OAuth (3LO) at the target level. MCP target types include Lambda functions, API Gateway REST APIs, OpenAPI specifications, Smithy models, MCP servers, and built-in integration provider templates. @@ -73,10 +72,0 @@ Use remote MCP servers to connect tools, prompts, and resources to your agent ru -**Integrations** - - -Use pre-configured templates from integration providers. - -**Connectors** - - -Use built-in connectors to tools. -