Question

A SaaS company builds a customer-support platform where each tenant can customize which foundation model, instructions, and set of tools their support assistant uses. Tenant configurations change frequently and are stored in DynamoDB. The team currently creates a separate Bedrock Agent (with DRAFT and versioned aliases) per tenant, but managing thousands of prepared agents has become operationally expensive and slow to update. They want to define the agent's model, instructions, and action groups dynamically at invocation time from the stored tenant config, without pre-provisioning agent resources. Which approach best meets this requirement?

Accepted Answer

Use the Bedrock Agents InvokeInlineAgent API, passing the tenant's foundation model, instructions, and action groups in the request payload so the agent is configured at runtime with no pre-created agent resource.

Answer

Create a single shared Bedrock Agent and use PrepareAgent before each invocation to inject the tenant-specific instructions and tools.

Answer

Continue creating one Bedrock Agent per tenant but automate provisioning with Step Functions to reduce operational effort.

Answer

Use the Converse API with tool use and manually implement the ReAct orchestration loop in Lambda for every tenant request.