Question

A retail company is building a customer support assistant using an Amazon Bedrock Agent that queries order data through an action group. The agent typically completes reasoning and tool invocations in 45-90 seconds. The frontend calls the agent through Amazon API Gateway backed by a Lambda function that invokes the InvokeAgent API. During peak load, users report that requests fail with 504 errors before receiving a response, even though the agent eventually completes successfully in CloudWatch traces. Which approach best resolves this while preserving the conversational experience?

Accepted Answer

Switch the Lambda function to call InvokeAgent with streaming enabled and stream partial agent responses back to the client over an API Gateway WebSocket API connection.

Answer

Increase the API Gateway REST API integration timeout to 120 seconds and raise the Lambda function timeout to match the longest agent execution.

Answer

Move the agent invocation into an AWS Step Functions Standard workflow triggered synchronously by API Gateway so the state machine holds the connection open until completion.

Answer

Add provisioned throughput to the agent's foundation model so that reasoning latency drops below the API Gateway 29-second integration timeout.