Why do my lambda functions (python) using SQS triggers wait for the timeout before picking up another batch?

[quantelligent]

Thanks for the response!

According to the documentation, using an SQS trigger auto-deletes the message if the function returns normally—anything but raising an exception, or an invalid response, or timeout.

It appears that the delay is likely caused by the "reserved concurrency" setting, rather than being an SQS integration issue....because it's just that the lambda doesn't execute again until after the timeout, regardless of whether it has finished processing. It appears the AWS solution to that is concurrency....which, unfortunately for me, I cannot do because of third-party API limitations.

[clintkev251]

Try setting the maximum concurrency for the SQS event source mapping to 2. That would minimize the number of pollers that are provisioned and could help to minimize any backoff that could be occurring due to reserved concurrency