Question

A developer builds a Lambda function that is triggered by messages arriving in an SQS queue. During traffic spikes, Lambda scales out to hundreds of concurrent executions, each of which opens a connection to a small Amazon RDS for PostgreSQL instance. The database quickly exhausts its maximum connection limit and begins rejecting queries, causing message processing to fail. The team wants a native Lambda configuration that limits how many instances of this function run at the same time without affecting other functions in the account. What should the developer do?

Accepted Answer

Set a reserved concurrency value on the function to cap the maximum number of simultaneous executions.

Answer

Enable provisioned concurrency on the function to pre-initialize a fixed number of execution environments.

Answer

Increase the function's memory allocation so each invocation completes faster and releases its database connection sooner.

Answer

Configure a longer function timeout so connections have more time to be reused across invocations.