A municipal permit queue grows because an SQS-triggered Lambda’s batch size and visibility timeout do not match how long each batch takes to process. What is the most likely integration problem?
Select an answer to reveal the explanation.
Short Explanation
Picture a ticket window that locks tickets for two minutes while clerks need five—the line explodes. Same story when SQS visibility timeout and Lambda batch size do not match real processing time.
Full Explanation
SQS event-source mappings expose batch size and interact with message visibility timeout. If visibility expires before the Lambda batch finishes, messages can reappear and the queue depth grows; oversized batches can also exceed processing time. Cognito MFA, CloudFront, and unused Kinesis streams are not the primary explanation for this SQS–Lambda mismatch.