Lambda function memory utilization below 25% of configured limit
- Severity
- Low
- Service
- Lambda
- Check ID
- LAMBDA_OVER_PROVISIONED_MEMORY
What this check finds
Lambda charges based on GB-seconds of memory allocated, not memory used. A function consistently using less than 25% of its configured memory is paying for 4× more memory than needed. Over-provisioned memory can be detected using the MaxMemoryUsed metric in CloudWatch and reduced without impacting performance.
Passing looks like: Lambda memory right-sized.
How to fix it
Reduce the function memory setting to approximately 1.5–2× the observed MaxMemoryUsed.
AWS CLI
aws lambda update-function-configuration --function-name FUNCTION_NAME --memory-size NEW_VALUE
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Lambda → Functions → select function → Configuration → General configuration → Edit → Memory.
Compliance
This is a cost check. It flags spend that buys nothing, which no compliance framework asks about, so it is not mapped to a control.
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs