Question

A financial services company is building a customer support assistant with Amazon Bedrock Agents. When a customer asks to cancel a pending wire transfer, the agent must call the bank's internal transfer-cancellation microservice. For security and compliance reasons, this microservice runs inside a private on-premises data center that is not reachable from AWS Lambda or any AWS-hosted compute, and the security team refuses to expose it via any public or VPC-connected endpoint that Bedrock could invoke. The team still wants the agent to orchestrate the conversation, determine when cancellation is needed, and extract the correct parameters. How should the developer configure the Bedrock Agent action group to satisfy these constraints?

Accepted Answer

Configure the action group to use return of control (RETURN_CONTROL executor), so Bedrock returns the identified action and extracted parameters to the calling application, which then invokes the on-premises microservice itself.

Answer

Configure the action group with a Lambda function executor and use AWS PrivateLink to reach the on-premises microservice, since Bedrock requires a Lambda for all action groups.

Answer

Attach an OpenAPI schema pointing directly at the on-premises microservice URL so the agent can call it over the internet after whitelisting Bedrock's IP ranges.

Answer

Use a Bedrock Knowledge Base to store the cancellation API definition and let the agent retrieve and execute it at runtime through RAG.