Bird
0
0

A Lambda function triggered by an S3 event is not running. The Lambda resource policy denies S3 access. What should be fixed?

medium📝 Debug Q7 of 15
AWS - Lambda
A Lambda function triggered by an S3 event is not running. The Lambda resource policy denies S3 access. What should be fixed?
AIncrease Lambda memory size
BUpdate the Lambda resource policy to allow S3 service to invoke the function
CChange the Lambda runtime to a supported version
DEnable versioning on the S3 bucket
Step-by-Step Solution
Solution:

  1. Step 1: Identify permission issue

    The Lambda resource policy denying S3 access blocks event notifications from triggering Lambda.

  2. Step 2: Correct the resource policy

    Allow S3 to invoke the Lambda function by updating the Lambda resource policy with proper permissions.

  3. Final Answer:

    Update the Lambda resource policy to allow S3 service to invoke the function -> Option B

  4. Quick Check:

    Lambda resource policy must allow S3 invocation [OK]
Quick Trick: Lambda resource policy must permit S3 invocation for triggers [OK]
Common Mistakes:
MISTAKES
  • Changing unrelated Lambda settings
  • Ignoring Lambda resource policy permissions
  • Assuming versioning affects triggers

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
API Gateway - Lambda integration - Quiz 5medium AWS Lambda - Lambda function concept - Quiz 12easy Auto Scaling - Cooldown periods - Quiz 13medium CloudWatch - CloudWatch metrics - Quiz 4medium DynamoDB - Scan vs query performance - Quiz 9hard Elastic Load Balancing - Listener rules and routing - Quiz 3easy RDS and Relational Databases - Read replicas for performance - Quiz 1easy RDS and Relational Databases - RDS backup and snapshots - Quiz 10hard SNS and SQS - SNS notification types (email, SMS, Lambda) - Quiz 9hard SNS and SQS - SNS and SQS integration pattern (fan-out) - Quiz 14medium