AWS connect: Restructure MCP server integration guide; add JWT audience and gateway setup
Summary
Rewrites the Amazon Connect Customer MCP server integration guide: adds an Integration identifier field, moves gateway creation into a new 'Create a gateway in Bedrock AgentCore' section, documents supported 2025 MCP protocol versions, and adds Inbound Identity configuration requiring the Integration identifier in the gateway's Allowed audiences (JWT aud claim).
Security assessment
The change documents authentication configuration for the Bedrock AgentCore gateway: it instructs admins to configure Inbound Identity with JWT and to place the Integration identifier in the Allowed audiences field so the gateway validates the token's aud claim. This is security-relevant hardening/guidance (token audience validation, protocol version pinning) but there is no evidence it addresses a specific vulnerability, CVE, or incident.
Evidence
Connect Customer sends a JWT to the gateway. The token's `aud` (audience) claim has the **Integration identifier**. If the gateway's audiences don't include this value, the gateway rejects the token, and tool calls fail.
Diff
diff --git a/connect/latest/adminguide/3p-apps-mcp-server.md b/connect/latest/adminguide/3p-apps-mcp-server.md index 9c26b70..fd2b307 100644 --- a//connect/latest/adminguide/3p-apps-mcp-server.md +++ b//connect/latest/adminguide/3p-apps-mcp-server.md @@ -7 +7 @@ -How to integrate an MCP server +How to integrate an MCP serverCreate a gateway in Bedrock AgentCore @@ -11 +11 @@ How to integrate an MCP server -To integrate an MCP server with Connect Customer, you must configure a Bedrock AgentCore gateway. The gateway transforms your APIs, Lambda functions, and services into MCP-compatible tools for AI agents. +To use an MCP server with Connect Customer, you need an Amazon Bedrock AgentCore gateway. The gateway turns your APIs, Lambda functions, and services into MCP tools. AI agents can use these tools. @@ -15 +15 @@ To integrate an MCP server with Connect Customer, you must configure a Bedrock A -Only one instance can be associated with a gateway, and that instance must be configured with the gateway's Discovery URL in Bedrock AgentCore. Each gateway can only be used with one MCP server. +Each gateway supports one MCP server and one instance. The instance must use the gateway's Discovery URL. For information about setting up the gateway, see Create a gateway in Bedrock AgentCore. @@ -19 +19 @@ Only one instance can be associated with a gateway, and that instance must be co - 1. On the **Add integration** page, enter the following information: + 1. On the **Add integration** page, enter the following details: @@ -23 +23 @@ Only one instance can be associated with a gateway, and that instance must be co - * **Display name** – A friendly name for the application. This name is displayed on security profiles and to your agents on the tab in the agent workspace. You can change this name later. + * **Display name** – A name for the integration. This name appears on security profiles. You can change it later. @@ -25 +25 @@ Only one instance can be associated with a gateway, and that instance must be co - * **Description (optional)** – You can optionally provide a description for this application. + * **Description** (optional) – A description of the integration. @@ -29 +29,7 @@ Only one instance can be associated with a gateway, and that instance must be co - + * **Integration identifier** – A unique ID for the integration. Use letters, numbers, hyphens (-), and underscores (_). You can't change it later. + +###### Note + +The **Integration identifier** doesn't need to match the gateway ID. You can use any value. Add the same value to the gateway's **Allowed audiences** field. + + @@ -33 +39 @@ Only one instance can be associated with a gateway, and that instance must be co -Select a Bedrock AgentCore gateway to connect with Connect Customer. Gateways convert APIs, Lambda functions, and services into MCP-compatible tools for AI agents. If no gateways currently exist, create a new one using Bedrock AgentCore. +Select a Bedrock AgentCore gateway to use with Connect Customer. If you don't have a gateway, choose **create a new one**. For more information about the gateway settings that Connect Customer requires, see Create a gateway in Bedrock AgentCore. @@ -37 +43 @@ Select a Bedrock AgentCore gateway to connect with Connect Customer. Gateways co -A new gateway can be created in Bedrock AgentCore. + 3. **Instance association** (optional) @@ -39 +45 @@ A new gateway can be created in Bedrock AgentCore. -###### Note +Select the instance that uses the gateway's Discovery URL. The default is **None**. You can skip this and add an instance later. @@ -41 +47 @@ A new gateway can be created in Bedrock AgentCore. -The Discovery URL must follow this format: `[connect instance URL]/.well-known/openid-configuration`. For example: `https://my-instance.my.connect.aws/.well-known/openid-configuration`. + @@ -43 +49 @@ The Discovery URL must follow this format: `[connect instance URL]/.well-known/o -###### Configure the gateway's Allowed audiences field + 2. Choose **Add integration**. @@ -45 +51 @@ The Discovery URL must follow this format: `[connect instance URL]/.well-known/o -In the gateway's **Inbound Identity** configuration, add the gateway ID to the **Allowed audiences** field. The JSON Web Token (JWT) that Connect Customer sends to the gateway carries the gateway ID in its `aud` (audience) claim. When the gateway ID is missing from **Allowed audiences** , the gateway rejects the token and tool invocations fail. + 3. After you add the integration, the **View integration** page opens. It shows a success notification and the **Integration details** section. @@ -47 +53 @@ In the gateway's **Inbound Identity** configuration, add the gateway ID to the * -**Allowed audiences** is the only field you must set for Connect Customer. You can leave the **Allowed clients** , **Allowed scopes** , and **Custom claims** fields empty. + @@ -49 +54,0 @@ In the gateway's **Inbound Identity** configuration, add the gateway ID to the * -###### Add a supported protocol version to the gateway @@ -51 +55,0 @@ In the gateway's **Inbound Identity** configuration, add the gateway ID to the * -The gateway's **Supported Versions** must include the Model Context Protocol (MCP) version that Connect Customer supports, which is `2025-03-26`. Gateways that you create or edit in the console must include protocol version `2025-03-26`. @@ -53 +56,0 @@ The gateway's **Supported Versions** must include the Model Context Protocol (MC -To add the supported version, edit the gateway in Amazon Bedrock AgentCore. In **Additional Configurations** , add `2025-03-26` to the **Supported Versions** field. @@ -55 +58 @@ To add the supported version, edit the gateway in Amazon Bedrock AgentCore. In * - +## Create a gateway in Bedrock AgentCore @@ -57 +60 @@ To add the supported version, edit the gateway in Amazon Bedrock AgentCore. In * - 3. **Instance association (optional)** +When you create a gateway in Bedrock AgentCore for Connect Customer, use the following settings. @@ -59 +62 @@ To add the supported version, edit the gateway in Amazon Bedrock AgentCore. In * -Select the instance that is configured with the selected gateway's Discovery URL. Defaults to **None**. If you are not ready to select an instance or if no instance has been associated with the selected gateway's Discovery URL, you might still create the MCP server integration now and associate an instance later. +###### Supported protocol versions @@ -61 +64 @@ Select the instance that is configured with the selected gateway's Discovery URL - +Connect Customer supports only 2025 Model Context Protocol (MCP) versions. The gateway's **Supported versions** must include one of the 2025 versions: `2025-03-26`, `2025-06-18`, or `2025-11-25`. @@ -63 +66,7 @@ Select the instance that is configured with the selected gateway's Discovery URL - 2. Choose **Add integration**. +When you create the gateway, expand **Additional configurations**. Then choose a 2025 version from the **Supported versions** list. You can't change the version later. If an existing gateway doesn't have a 2025 version, create a new one. + + + +###### Note + +The Discovery URL must use this format: `[connect instance URL]/.well-known/openid-configuration`. For example: `https://my-instance.my.connect.aws/.well-known/openid-configuration`. @@ -65 +74 @@ Select the instance that is configured with the selected gateway's Discovery URL - 3. If the integration was successfully created, you will be sent to the **View integration** page where you will see a success banner and the integration summary. +###### Allowed audiences @@ -67 +76 @@ Select the instance that is configured with the selected gateway's Discovery URL - +On the **Configure Inbound Identity** page, choose **Use JSON Web Tokens (JWT)** and **Use existing Identity provider configurations**. Under **Allowed audiences** , enter your **Integration identifier** in the **Audiences** field. @@ -68,0 +78 @@ Select the instance that is configured with the selected gateway's Discovery URL +Connect Customer sends a JWT to the gateway. The token's `aud` (audience) claim has the **Integration identifier**. If the gateway's audiences don't include this value, the gateway rejects the token, and tool calls fail. @@ -69,0 +80 @@ Select the instance that is configured with the selected gateway's Discovery URL +**Allowed audiences** is the only field that Connect Customer needs. You can leave the **Allowed clients** , **Allowed scopes and advertised values** , and **Custom claims** fields empty. @@ -70,0 +82 @@ Select the instance that is configured with the selected gateway's Discovery URL +