AWS bedrock-agentcore documentation change
Summary
Updated authorization support matrix and added specific configuration requirements for IAM-based outbound authorization with MCP server targets, including required SigV4 signing parameters.
Security assessment
The changes clarify authorization capabilities for different target types (API Gateway, MCP server, Smithy schema) and add detailed configuration instructions for IAM-based authentication with MCP servers. This enhances security documentation by specifying required SigV4 signing parameters (service name, region) for MCP server targets, which improves authentication security. No evidence of a security vulnerability being addressed.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-outbound-auth.md b/bedrock-agentcore/latest/devguide/gateway-outbound-auth.md index 5df35cdf1..82f0f2eed 100644 --- a//bedrock-agentcore/latest/devguide/gateway-outbound-auth.md +++ b//bedrock-agentcore/latest/devguide/gateway-outbound-auth.md @@ -32 +32 @@ Target type | No authorization | Gateway service role | OAuth (client credential -API Gateway stage | No | Yes | No | No | Yes +API Gateway stage | Yes | Yes | No | No | Yes @@ -34 +34 @@ Lambda function | No | Yes | No | No | No -MCP server | Yes | No | Yes | No | No +MCP server | Yes | Yes | Yes | No | No @@ -36 +36 @@ OpenAPI schema | No | No | Yes | Yes | Yes -Smithy schema | No | Yes | Yes | Yes | No +Smithy schema | No | Yes | Yes | No | No @@ -63 +63 @@ Select a topic to learn how to set up that type of authorization: -IAM-based outbound authorization lets you use the gateway service role's IAM credentials to authorize with [AWS Signature Version 4 (Sig V4)](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html). This option lets the Amazon Bedrock AgentCore service to authenticate to gateway targets on your gateway callers' behalf. +IAM-based outbound authorization lets you use the gateway service role's IAM credentials to authorize with [AWS Signature Version 4 (Sig V4)](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html). This option lets the Amazon Bedrock AgentCore service authenticate to gateway targets on your gateway callers' behalf. @@ -65 +65,14 @@ IAM-based outbound authorization lets you use the gateway service role's IAM cre -If you use this option, make sure that the gateway service role has `bedrock-agentcore:InvokeGateway` permissions. The service role's credentials will be used for authentication during gateway invocation. +If you use this option, verify that the gateway service role has `bedrock-agentcore:InvokeGateway` permissions. The gateway uses the service role credentials for authentication during invocation. + +**Additional configuration for MCP server targets** + +When you use IAM-based outbound authorization with an MCP server target, you must provide additional configuration for SigV4 signing. In the `credentialProviderConfigurations`, include an `iamCredentialProvider` with the following fields: + + * **service** (required) – The AWS service name used for SigV4 signing. For example, `bedrock-agentcore` for MCP servers hosted on Amazon Bedrock AgentCore. + + * **region** (optional) – The AWS Region for SigV4 signing. If you don't specify a Region, the gateway uses its own Region. + + + + +For Lambda, API Gateway, and Smithy targets, do not include the `iamCredentialProvider` field. These target types only support the basic `GATEWAY_IAM_ROLE` configuration with `credentialProviderType` only. For more information about specifying the credential provider configuration, see [AgentCore Gateway service role (IAM) authorization](./gateway-building-adding-targets-authorization.html#gateway-building-adding-targets-authorization-service-role).