Incorrect Finding Reason Codes for NotOptimized Function Configuration

[KSN2003]

Describe the issue

The function has been flagged with a NotOptimized finding classification, indicating that its configuration is not aligned with the actual workload requirements—either due to over-provisioning or under-provisioning of resources. However, the issue description incorrectly lists the reason codes as MemoryUnderprovisioned twice, instead of including both MemoryUnderprovisioned and MemoryOverprovisioned.

Links

https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/compute-optimizer/client/get_lambda_function_recommendations.html

[adev-code]

Hello @KSN2003, thanks for reaching out. I have reached out to the Compute Optimize Service Team for an update. Moving forward, please ensure to check our documentation for updates and also changelog. Feedback can also be sent directly to the team via the API documentation. Thank you.

For Internal Tracking: P277416986

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.