A development team deployed a new Lambda function 15 minutes ago and it has been invoked multiple times, but there are no log entries in CloudWatch Logs. Which of the following is a likely reason?

The most likely reason for missing CloudWatch Logs entries is insufficient IAM permissions. For a Lambda function to send logs to CloudWatch, its execution role must have permissions like logs:CreateLogGroup, logs:CreateLogStream, and logs:PutLogEvents. Without these, Lambda cannot create the necessary log resources or write log data. While developers might not have explicit logging statements, Lambda automatically emits basic runtime logs (e.g., START, END, REPORT lines) which would still appear if permissions were correct. If the function throws an exception, error details would typically be logged by Lambda itself, assuming proper permissions. Lambda functions do not write logs to local files that require separate shipping; logs are directly integrated with CloudWatch Logs.