Over-provisioned Lambda memory

A Lambda function allocated more memory than its invocation metrics justify.

Last updated July 3, 2026

What triggers this finding

A Lambda function with at least 512 MB of memory, more than 1,000 invocations in the lookback window, and average duration under 200 ms — indicating memory is likely over-allocated.

Typical fix

Reduce memory allocation toward 128–256 MB and re-test. Lambda bills proportionally to memory, so rightsizing can cut cost without hurting performance.

Example savings

Varies by invocation volume — flagged when estimated monthly cost is at least $1; high-traffic functions can save $50+/month.

See also: Severity and savings estimates for how Parsivex calculates figures on your report.

Related articles