1
Verify the likely cause
Create the client outside the handler, release connections, inspect proxy borrow latency and cap reserved concurrency to database capacity.
FULL AI ANALYSIS
AWS Lambda intermittently cannot reach RDS after scaling
Generated Sep 23, 2026, 11:55:04 AM
Analysis summary
The reported behaviour is consistent with connections are not reused correctly or the proxy pool is exhausted during concurrency spikes. The safest next step is to verify that hypothesis with a reversible test before making permanent configuration changes.
Possible causes
Connections are not reused correctly or the proxy pool is exhausted during concurrency spikes.
81%A recent software, firmware or configuration change is exposing an existing compatibility issue.
33%Suggested fixes
2
Validate and monitor
Reproduce the issue once after the change, review relevant logs or metrics, and keep a rollback path until the system has remained stable.