Optional ReadonlyauthorizerInbound authorization configuration (shared with the AgentCore Runtime module). Provide
customJwt for JWT/OIDC inbound auth, or omit it to use AWS IAM (SigV4). MDAA does not support
NONE or AUTHENTICATE_ONLY.
Use cases: inbound access control
AWS: AWS::BedrockAgentCore::Gateway AuthorizerType + AuthorizerConfiguration
Validation: Optional; valid customJwt when present (see AgentcoreAuthorizerConfigProperty)
Optional ReadonlydescriptionDescription of the gateway.
Use cases: documentation, operational clarity
AWS: AWS::BedrockAgentCore::Gateway Description
Validation: Optional; String; 1-200 characters (AWS documents no character-set restriction)
Optional ReadonlyexceptionException level. Only DEBUG is settable; omit to leave the secure service default (INFO).
DEBUG surfaces more exception detail in responses/logs (possibly sensitive internal error and
request context), so use it only for troubleshooting, not in production.
Use cases: troubleshooting
AWS: AWS::BedrockAgentCore::Gateway ExceptionLevel
Validation: Optional; 'DEBUG'
Optional ReadonlyinterceptorsLambda interceptors (at most one REQUEST and one RESPONSE).
Use cases: per-tool authorization, request/response transformation
AWS: AWS::BedrockAgentCore::Gateway InterceptorConfigurations
Validation: Optional; GatewayInterceptorConfigurationsProperty[]; max 2 (one per interception point)
Optional ReadonlylogGateway audit log delivery. Omit for the compliant default (a CMK-encrypted CloudWatch Logs destination log group plus a vended delivery pipeline on the gateway ARN, indefinite retention).
Use cases: audit logging, retention tuning, opt-out
AWS: CloudWatch Logs vended delivery (DeliverySource / DeliveryDestination / Delivery)
Validation: Optional; GatewayLogDeliveryProperty
Optional ReadonlyprotocolMCP protocol configuration (instructions, search type, supported versions). MCP is the only
protocol the service supports, so protocolType is always MCP (set by the construct). When
omitted, the gateway applies the service default (semantic search off). Semantic search is
immutable after creation, so enable it here at creation time if needed.
Use cases: tool discovery semantics, semantic search
AWS: AWS::BedrockAgentCore::Gateway ProtocolConfiguration.Mcp
Validation: Optional; McpProtocolConfigurationProperty
Optional ReadonlyroleReference to an existing IAM role for the gateway execution role (by name, arn, or id).
If omitted, MDAA auto-creates an MdaaRole with a scoped trust policy. Either way MDAA attaches
the gateway's required execution permissions (interceptor lambda:InvokeFunction when
configured; no CloudWatch Logs permissions, as gateways log via vended delivery) — there is no
separate "extra policies" field. To grant more, add it to the referenced role's own definition.
Use cases: role reuse via a single fully-defined role, or auto-created in place
AWS: AWS::BedrockAgentCore::Gateway RoleArn
Validation: Optional; MdaaRoleRef
Configuration for a Bedrock AgentCore Gateway — a managed MCP server fronting an agent's tools. MDAA enforces compliance-by-default: an always-on customer-managed KMS CMK, the inbound authorizer restricted to CUSTOM_JWT or AWS_IAM, and scoped customer-managed execution policies.
Use cases: unified MCP tool surface, per-tool authorization via interceptors, compliant gateway deployment
AWS: Amazon Bedrock AgentCore Gateway
Validation: authorizerConfiguration is optional (omit customJwt for AWS IAM)
Name-less base of the gateway config surface (every field except
gatewayNameandtargets), so an orchestrating module (bedrock-builder) can key a gateway by name and add its own target-reference model, while BedrockAgentcoreGatewayProps addsgatewayName/targetsback for direct use. (jsii forbidsOmit/Pick, hence a hand-authored base interface rather than a derived type.)