Optional ReadonlysecuritySecurity group for the connector, when the set marks bedrockAgentRuntime external: the module then
has no endpoint to wire, so this group must already allow HTTPS to wherever Retrieve is reached.
Use cases: an endpoint whose security group is managed by a central networking team
AWS: AWS::Lambda::Function VpcConfig.SecurityGroupIds
Validation: Required when the set marks bedrockAgentRuntime external, and not allowed otherwise
ReadonlysubnetsSubnets the connector's network interfaces are placed in, in the VPC of the vpcEndpoints set.
Use cases: placing the connector in private subnets
AWS: AWS::Lambda::Function VpcConfig.SubnetIds
Validation: Required; String[]; 1-16 entries
ReadonlyvpcName of the set in the module's vpcEndpoints map the connector reaches Retrieve through. When the
set creates the Bedrock Agent Runtime endpoint or brings an existing one, the module creates the
connector's security group with HTTPS access to it; when the set marks it external, set
securityGroupId.
Use cases: a private path to Retrieve with no NAT
AWS: AWS::EC2::VPCEndpoint (bedrock-agent-runtime)
Validation: Required; String; a key in vpcEndpoints
VPC placement of a knowledge base connector. The connector runs in
subnets, in the VPC of thevpcEndpointsset it references. When the set creates or brings the Bedrock Agent Runtime endpoint, the connector calls Retrieve through it, so its requests carryaws:SourceVpcandaws:SourceVpce; when the set marks it external, the network path is yours.Use cases: an organization policy that requires Lambda functions to be VPC-bound (
lambda:VpcIds); data perimeter policies that requireaws:SourceVpcoraws:SourceVpceonbedrock:RetrieveAWS: AWS::Lambda::Function VpcConfig
Validation:
subnetsandvpcEndpointsrequired