Explanation:
Lambda execution role needs logs:CreateLogGroup, logs:CreateLogStream, logs:PutLogEvents to write to CloudWatch Logs. If missing, no logs even if invoked. Other causes possible but permission is common. Logs are enabled by default.
Ultimate access to all questions.
No comments yet.
A Lambda function was deployed 15 minutes ago and invoked many times, but no log messages appear in CloudWatch Logs. What is one cause?
A
Developers did not enable log messages for this Lambda function.
B
The Lambda function's role does not include permissions to create CloudWatch Logs items.
C
The Lambda function raises an exception before the first log statement.
D
Lambda creates local log files that must be shipped to CloudWatch Logs first.