AWS Security ChangesHomeSearch

AWS connect: Clarify MCP server integration and JWT audience config

Service: connect · 2026-11-05 · Documentation medium

File: connect/latest/adminguide/3p-apps-mcp-server.md · Type: authz

Summary

Reworded and restructured the MCP server integration guide for Connect Customer, adding explicit sections on configuring the Bedrock AgentCore gateway's Allowed audiences field (JWT aud claim) and on adding the supported MCP protocol version 2025-03-26, plus general wording/step cleanup.

Security assessment

The added content documents token-validation configuration: the gateway's Allowed audiences must contain the gateway ID because the JWT sent by Connect Customer carries it in the `aud` claim, otherwise the gateway rejects the token. This is security-adjacent authz/JWT guidance rather than a fix for a specific vulnerability or incident, so it is not security_issue_related but does add security documentation.

Evidence

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.

Diff

diff --git a/connect/latest/adminguide/3p-apps-mcp-server.md b/connect/latest/adminguide/3p-apps-mcp-server.md
index fd2b307..9c26b70 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 serverCreate a gateway in Bedrock AgentCore
+How to integrate an MCP server
@@ -11 +11 @@ How to integrate an MCP serverCreate a gateway in Bedrock AgentCore
-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.
+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.
@@ -15 +15 @@ To use an MCP server with Connect Customer, you need an Amazon Bedrock AgentCore
-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.
+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.
@@ -19 +19 @@ Each gateway supports one MCP server and one instance. The instance must use the
-  1. On the **Add integration** page, enter the following details:
+  1. On the **Add integration** page, enter the following information:
@@ -23 +23 @@ Each gateway supports one MCP server and one instance. The instance must use the
-       * **Display name** – A name for the integration. This name appears on security profiles. You can change it later.
+       * **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.
@@ -25 +25 @@ Each gateway supports one MCP server and one instance. The instance must use the
-       * **Description** (optional) – A description of the integration.
+       * **Description (optional)** – You can optionally provide a description for this application.
@@ -29,7 +29 @@ Each gateway supports one MCP server and one instance. The instance must use the
-       * **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.
-
-![The Add integration page showing the Integration information fields for an MCP server.](/images/connect/latest/adminguide/images/integrations-3p-mcp-app.png)
+![The Add integration page showing Integration information fields for an MCP server application.](/images/connect/latest/adminguide/images/integrations-3p-mcp-app.png)
@@ -39 +33 @@ The **Integration identifier** doesn't need to match the gateway ID. You can use
-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.
+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.
@@ -43,5 +37 @@ Select a Bedrock AgentCore gateway to use with Connect Customer. If you don't ha
-    3. **Instance association** (optional)
-
-Select the instance that uses the gateway's Discovery URL. The default is **None**. You can skip this and add an instance later.
-
-![The Instance association section showing instance selection options.](/images/connect/latest/adminguide/images/3p-apps-mcp-instance.png)
+A new gateway can be created in Bedrock AgentCore.
@@ -49,3 +39 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
-  2. Choose **Add integration**.
-
-  3. After you add the integration, the **View integration** page opens. It shows a success notification and the **Integration details** section.
+###### Note
@@ -53 +41 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
-![The View integration page in the Connect Customer console with a success notification and the Integration details section.](/images/connect/latest/adminguide/images/3p-apps-mcp-success.png)
+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`.
@@ -54,0 +43 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
+###### Configure the gateway's Allowed audiences field
@@ -55,0 +45 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
+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.
@@ -56,0 +47 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
+**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.
@@ -58 +49 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
-## Create a gateway in Bedrock AgentCore
+###### Add a supported protocol version to the gateway
@@ -60 +51 @@ Select the instance that uses the gateway's Discovery URL. The default is **None
-When you create a gateway in Bedrock AgentCore for Connect Customer, use the following settings.
+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`.
@@ -62 +53 @@ When you create a gateway in Bedrock AgentCore for Connect Customer, use the fol
-###### Supported protocol versions
+To add the supported version, edit the gateway in Amazon Bedrock AgentCore. In **Additional Configurations** , add `2025-03-26` to the **Supported Versions** field.
@@ -64 +55 @@ When you create a gateway in Bedrock AgentCore for Connect Customer, use the fol
-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`.
+![Additional gateway configuration options.](/images/connect/latest/adminguide/images/3p-apps-mcp-bedrock.png)
@@ -66 +57 @@ Connect Customer supports only 2025 Model Context Protocol (MCP) versions. The g
-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.
+    3. **Instance association (optional)**
@@ -68 +59 @@ When you create the gateway, expand **Additional configurations**. Then choose a
-![The Define gateway details page in Bedrock AgentCore with a 2025 version selected in Supported versions.](/images/connect/latest/adminguide/images/3p-apps-mcp-bedrock.png)
+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.
@@ -70 +61 @@ When you create the gateway, expand **Additional configurations**. Then choose a
-###### Note
+![The Instance association section showing instance selection options.](/images/connect/latest/adminguide/images/3p-apps-mcp-instance.png)
@@ -72 +63 @@ When you create the gateway, expand **Additional configurations**. Then choose a
-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`.
+  2. Choose **Add integration**.
@@ -74 +65 @@ The Discovery URL must use this format: `[connect instance URL]/.well-known/open
-###### Allowed audiences
+  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.
@@ -76 +67 @@ The Discovery URL must use this format: `[connect instance URL]/.well-known/open
-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.
+![The View integration page showing a success banner after integrating an MCP server.](/images/connect/latest/adminguide/images/3p-apps-mcp-success.png)
@@ -78 +68,0 @@ On the **Configure Inbound Identity** page, choose **Use JSON Web Tokens (JWT)**
-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.
@@ -80 +69,0 @@ Connect Customer sends a JWT to the gateway. The token's `aud` (audience) claim
-**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.
@@ -82 +70,0 @@ Connect Customer sends a JWT to the gateway. The token's `aud` (audience) claim
-![The Configure Inbound Identity page in Bedrock AgentCore with the Integration identifier entered in the Audiences field.](/images/connect/latest/adminguide/images/3p-apps-mcp-bedrock-inbound-identity.png)