Check if Lambda runs as Admin
Ensure that your Amazon Lambda functions do not have administrative permissions in order to promote the Principle of Least Privilege.
Your number of Lambda can grow pretty fast - and so could be your painpoints.
Ensure that your Amazon Lambda functions do not have administrative permissions in order to promote the Principle of Least Privilege.
Identify any publicly accessible AWS Lambda functions and update their access policy in order to protect against unauthorized users that are sending requests to invoke these functions.
Is the dead letter queue (DLQ) configured for Lambda functions?
Is default timeout used for Lambda functions?
Are you using aliasing for Lambda functions?
Are there too many versions for any Lambda function?
Is your function runtime up to date?
Is your function using a runtime which is coming up for deprecation?
Is the tracing mode function enabled?
Using An IAM Role For More Than One Lambda Function
Check if Lambda functions invoke API operations are being recorded by CloudTrail
Check if tags are setup on the Lambda function
Ensure there is no unauthorized cross-account access
Ensure that your Amazon Lambda functions have access to VPC-only resources
If you are not yet convinced to sign up with Cloudanix, that's not a problem. We recommend you use a comprehensive checklist which your team can use to perform a manual assessment of your workload.