A developer configures an SQS queue as a Lambda trigger but the Lambda is not invoked. What is a likely cause?

medium📝 Debug Q6 of 15

AWS - Lambda

AThe Lambda execution role lacks permission to read from the SQS queue

BThe SQS queue is encrypted with a KMS key Lambda cannot access

CThe Lambda function timeout is set too high

DThe Lambda function is in a different AWS region than the SQS queue

Step-by-Step Solution

Solution:

Step 1: Check Lambda permissions for SQS
Lambda needs permission to poll and read messages from the SQS queue via its execution role.
Step 2: Evaluate other options
Encryption or region mismatch can cause issues but permission is the most common cause; timeout being high does not prevent invocation.
Final Answer:
The Lambda execution role lacks permission to read from the SQS queue -> Option A
Quick Check:
Missing Lambda SQS read permission = no invocation [OK]

Quick Trick: Lambda needs read permission on SQS to trigger properly [OK]

Common Mistakes:

Master "Lambda" in AWS

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More AWS Quizzes