Question

A developer is building a document summarization feature exposed through Amazon API Gateway (REST) backed by a Lambda function that calls Amazon Bedrock. Users upload large PDFs that are extracted to text, sometimes exceeding 8 MB of extracted content, and summarization occasionally takes 90 seconds. Clients report HTTP 500 errors and truncated responses on large documents. The team must deliver a reliable synchronous-feeling experience without changing the client's ability to poll for results. Which architecture change best addresses both the payload size and latency limits?

Accepted Answer

Have the client upload the PDF directly to S3 via a presigned URL, invoke Lambda asynchronously to run Bedrock summarization, store the result in DynamoDB, and expose a separate GET endpoint the client polls for the completed summary.

Answer

Increase the Lambda function timeout to 15 minutes and raise the API Gateway integration timeout, then return the full summary in the initial synchronous response.

Answer

Enable Bedrock streaming with InvokeModelWithResponseStream and stream tokens back through the standard API Gateway REST integration to avoid the response size limit.

Answer

Compress the extracted text with gzip before passing it to Bedrock and enable API Gateway payload compression so the response fits within the limit.