Question

A developer's Lambda function connects to an Amazon RDS PostgreSQL database. Under moderate load, X-Ray traces show that each invocation spends 200-400ms establishing a new database connection, and the RDS instance is reporting an unusually high number of active connections that occasionally exhausts the connection limit. The developer wants to reduce both the per-invocation latency and the connection count without changing the database engine. Which change is the MOST effective?

Accepted Answer

Move the database connection creation outside the handler function so the connection is initialized once per execution environment and reused across invocations.

Answer

Increase the Lambda function's memory allocation so the connection is established faster on each invocation.

Answer

Set the Lambda function's reserved concurrency to a very high value so more environments are available to handle connections.

Answer

Open and close the database connection inside the handler on every invocation to ensure connections are always released.