Question

A financial services company is building a loan pre-approval system. The workflow is fully deterministic: validate applicant data, call a credit-scoring microservice, run a fixed set of eligibility rules, then generate a personalized rejection or approval letter using a Bedrock foundation model. The sequence of steps never changes, and the compliance team requires that every step be auditable and reproducible with explicit branching logic. Which implementation approach best fits these requirements?

Accepted Answer

Use AWS Step Functions to orchestrate the fixed sequence, invoking Lambda functions for validation, credit scoring, and eligibility rules, and calling Bedrock only for the final letter-generation step.

Answer

Build a Bedrock Agent with action groups for each step and let the agent's LLM-based orchestration decide the order of validation, scoring, and rule evaluation at runtime.

Answer

Use a single large prompt that instructs the foundation model to perform validation, credit scoring, eligibility evaluation, and letter generation in one InvokeModel call.

Answer

Implement the entire workflow inside one Lambda function using sequential synchronous calls with no external orchestration service.