Hi Team,
We have a general monitor configured to track all AWS Lambda functions using the metric aws.lambda.enhanced.out_of_memory. On 20 March, this monitor flagged one of our Lambda functions (webhooks) as experiencing an out-of-memory issue.
However, after investigating:
We have a dedicated monitor for the webhooks Lambda using the metric aws.lambda.enhanced.max_memory_used, and it has not indicated any abnormal memory usage.
We reviewed the logs in Amazon CloudWatch for that day and found no evidence of out-of-memory errors or related failures.
The Lambda function appears to be operating within expected memory limits.
On below screenshot is shown the errors coming up from the shared monitor for webhooks lambda,

While in the other hand the monitor that uses 'aws.lambda.enhanced.max_memory_used' metric shows that there were no spikes,

Also the same results coming from AWS Cloud Watch,

Hi Team,
We have a general monitor configured to track all AWS Lambda functions using the metric aws.lambda.enhanced.out_of_memory. On 20 March, this monitor flagged one of our Lambda functions (webhooks) as experiencing an out-of-memory issue.
However, after investigating:
We have a dedicated monitor for the webhooks Lambda using the metric aws.lambda.enhanced.max_memory_used, and it has not indicated any abnormal memory usage.
We reviewed the logs in Amazon CloudWatch for that day and found no evidence of out-of-memory errors or related failures.
The Lambda function appears to be operating within expected memory limits.
On below screenshot is shown the errors coming up from the shared monitor for webhooks lambda,

While in the other hand the monitor that uses 'aws.lambda.enhanced.max_memory_used' metric shows that there were no spikes,

Also the same results coming from AWS Cloud Watch,
