AWS - Serverless Architecture
You configured an S3 bucket to trigger a Lambda function on object creation, but the Lambda is not invoked. What is the most likely cause?
You configured an S3 bucket to trigger a Lambda function on object creation, but the Lambda is not invoked. What is the most likely cause?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check permissions for S3 to invoke Lambda
S3 must have permission to invoke the Lambda function via a resource-based policy on Lambda.Step 2: Understand common misconfigurations
Missing this permission causes Lambda not to trigger even if bucket notifications are set.Final Answer:
The S3 bucket notification configuration is missing permission for S3 to invoke Lambda. -> Option AQuick Check:
S3 needs invoke permission on Lambda [OK]
Quick Trick: Grant S3 permission to invoke Lambda in Lambda's resource policy [OK]
Common Mistakes:
- Confusing Lambda execution role with S3 invoke permission
- Assuming code errors prevent invocation
- Thinking region mismatch blocks invocation
Master "Serverless Architecture" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes