AWS solutions documentation change
Summary
Added MCP Server deployment option, expanded gateway method to include MCP Server targets, added new configuration fields for MCP Server URLs, and updated section numbering/references.
Security assessment
Changes focus on feature expansion (adding MCP Server support) and documentation structure updates. No security vulnerabilities, patches, or security-specific configurations are mentioned. The MCP Server URL requirement references standard protocol versions without security implications.
Diff
diff --git a/solutions/latest/generative-ai-application-builder-on-aws/step-3-deploy-a-use-case-using-deployment-dashboard-wizard.md b/solutions/latest/generative-ai-application-builder-on-aws/step-3-deploy-a-use-case-using-deployment-dashboard-wizard.md index 8486cca82..09242c2ca 100644 --- a//solutions/latest/generative-ai-application-builder-on-aws/step-3-deploy-a-use-case-using-deployment-dashboard-wizard.md +++ b//solutions/latest/generative-ai-application-builder-on-aws/step-3-deploy-a-use-case-using-deployment-dashboard-wizard.md @@ -14,0 +15,2 @@ In the Deployment dashboard wizard, you must choose between the following: + * MCP Server \- Deploy and manage MCP servers with gateway or runtime methods + @@ -42,0 +45,4 @@ When you choose **Create Text use case** , the UI opens the **Select use case** +### Use case details + +The use case details step allows you to configure additional settings for your deployment. + @@ -270 +276 @@ Before deploying an MCP Server use case, ensure that you have the following: - * **For Gateway method (Lambda/API)** : Lambda functions or API endpoints with their corresponding schema files (JSON format for Lambda, OpenAPI/Smithy for APIs) + * **For Gateway method (Lambda/API/MCP Server)** : Lambda functions, API endpoints with their corresponding schema files (JSON format for Lambda, OpenAPI/Smithy for APIs), or MCP Server URL endpoints @@ -281 +287 @@ The solution supports two methods for creating MCP servers: -**Create from Lambda or API (Gateway method)** +**Create from Lambda, API, or MCP Server (Gateway method)** @@ -283 +289 @@ The solution supports two methods for creating MCP servers: -This method creates an MCP gateway that wraps existing Lambda functions or REST APIs, making them accessible as MCP tools. The gateway handles protocol translation between MCP and your existing services. +This method creates an MCP gateway that wraps existing Lambda functions, REST APIs, or external MCP servers, making them accessible as MCP tools. The gateway handles protocol translation between MCP and your existing services. @@ -290,0 +297,2 @@ This method creates an MCP gateway that wraps existing Lambda functions or REST + * **MCP Server targets** : Connect directly to external MCP servers via URL endpoints, allowing integration of existing MCP servers without deploying new infrastructure + @@ -329 +337 @@ Choose between the two creation methods: - * **Create from Lambda or API** : Create an MCP gateway from existing Lambda functions or API specifications + * **Create from Lambda, API, or MCP Server** : Create an MCP gateway from existing Lambda functions, API specifications, or external MCP server endpoints @@ -340 +348 @@ The creation method cannot be changed after deployment. If you need to switch me -**Gateway Configuration (for Lambda/API method)** +**Gateway Configuration (for Lambda/API/MCP Server method)** @@ -355,0 +364,2 @@ If you selected the Gateway method, configure one or more targets: + * **MCP Server** : For direct connection to external MCP servers via URL endpoints + @@ -366 +376,3 @@ If you selected the Gateway method, configure one or more targets: - 6. **Outbound Authentication** (required for OpenAPI targets): Configure authentication for REST API calls: + 6. **MCP Server URL** (required for MCP Server targets): The URL endpoint of the external MCP server to connect to. The URL must be properly encoded and the MCP server must support tool capabilities with MCP protocol versions 2025-06-18. For more information, see [MCP servers targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html) in the _Amazon Bedrock AgentCore Developer Guide_. + + 7. **Outbound Authentication** (required for OpenAPI targets): Configure authentication for REST API calls: @@ -412 +424 @@ MCP Server deployments create resources in Amazon Bedrock AgentCore, including g -### Step 3c: Deploy an Agent Builder use case +### Step 3d: Deploy an Agent Builder use case @@ -424 +436 @@ This step is the same as the Text use case described previously. -This step is the same as the Text use case [described previously](./.html#use-case-details). +This step is the same as the Text use case described previously. @@ -473 +485 @@ After this step, review the settings you selected and choose **Deploy Use Case** -### Step 3d: Deploy a Workflow use case +### Step 3e: Deploy a Workflow use case @@ -485 +497 @@ This step is the same as the Text use case described previously. -This step is the same as the Text use case [described previously](./.html#use-case-details). +This step is the same as the Text use case described previously.