AWS - Serverless Architecture
You set up an S3 event notification to trigger a Lambda function on object creation, but the Lambda is never invoked. Which of the following is the most probable cause?
You set up an S3 event notification to trigger a Lambda function on object creation, but the Lambda is never invoked. Which of the following is the most probable cause?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Check permissions
S3 must have permission to invoke the Lambda function. This is controlled by the Lambda resource policy.Step 2: Evaluate other options
Bucket versioning is unrelated to event triggers. Missing handler causes runtime errors but not invocation failure. Cross-region triggers are supported but require proper configuration.Final Answer:
The Lambda function's execution role lacks permission to be invoked by S3 -> Option AQuick Check:
Lambda must allow S3 to invoke it via permissions [OK]
Quick Trick: Lambda needs permission for S3 to invoke it [OK]
Common Mistakes:
- Assuming versioning affects event triggers
- Confusing execution role with resource policy
- Ignoring cross-region invocation capabilities
Master "Serverless Architecture" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes