You’ve developed a Lambda function and now want to debug it, after the execution completes. You add the necessary print statements in the code to assist in the debugging process. You go to Cloudwatch logs but there are no logs for the Lambda function. Which of the following could be the underlying issue for this?

Answer options:

A.You’ve not enabled versioning for the Lambda function.
B.The IAM role needed for the lambda function to write the logs to Cloudwatch logs does not have the necessary permissions.
C.There is not enough memory assigned to the function.
D.There is not enough time assigned to the function.

Answer – B
The AWS Documentation mentions the following.
Note
"If your Lambda function code is executing, but you don`t see any log data being generated after several minutes, this could mean your execution role for the Lambda function did not grant permissions to write log data to CloudWatch Logs. For information about how to make sure that you have set up the execution role correctly to grant these permissions, see Manage Permissions: Using an IAM Role (Execution Role)".
Option A is incorrect since versioning will not help in this case.
Options C and D are incorrect since these were the cases if the function would not complete execution, but the question says debugging starts after the execution is completed.
For more information on monitoring Lambda functions, please refer to the below URL-
https://docs.aws.amazon.com/lambda/latest/dg/monitoring-functions.html