Question

A developer builds a Bedrock Agent whose action group invokes a Lambda function that queries an internal inventory database. During testing, some queries return large result sets and the agent fails intermittently with errors, while smaller queries succeed. CloudWatch logs show the Lambda executes successfully and returns a JSON body, but the agent orchestration step errors out before generating a final response. What is the MOST likely cause and the appropriate fix?

Accepted Answer

The Lambda function response exceeds the Bedrock Agent action group response payload size limit; redesign the function to paginate, filter, or summarize results so the returned payload stays within the limit.

Answer

The Lambda function timeout is too short for large queries; increase the Lambda timeout to 15 minutes so all result sets can be returned.

Answer

The agent's foundation model context window is too small; switch to a model with a larger context window so the agent can accept any response size.

Answer

The action group OpenAPI schema is missing a response definition; add a 200 response schema so the agent can parse arbitrarily large payloads.