AWS Lambda function trigger on object creation in S3 does not work

Question

I am doing an upload like this:

curl -v -X PUT -T "test.xml" -H "Host: my-bucket-upload.s3-eu-central-1.amazonaws.com" -H "Content-Type: application/xml" https://my-bucket-upload.s3-eu-central-1.amazonaws.com/test.xml

The file gets uploaded and I can see it in my S3 bucket.

The trick is, when I try to create a lambda function to be triggered on creation, it never gets invoked. If I upload the file using the S3 web interface, it works fine. What am I doing wrong? Is there any clear recipe on how to do it?

There are various events for adding new objects. can you show the lambda trigger configuration? — johni
– johni, Commented May 23, 2017 at 13:55

notionquest · Accepted Answer · 2017-05-23 16:23:22Z

3

Amazon S3 APIs such as PUT, POST, and COPY can create an object. Using these event types, you can enable notification when an object is created using a specific API, or you can use the s3:ObjectCreated:* event type to request notification regardless of the API that was used to create an object.

Check the notification event setup on the bucket
Go to bucket on AWS management console
Click the properties tab on the bucket
Click the Events to check the notification event setup

Case 1:

s3:ObjectCreated:* - Lambda should be invoked regardless of PUT, POST or COPY

Other case:-

If the event is setup for specific HTTP method, use that method on your CURL command to create the object on S3 bucket. This way it should trigger the Lambda function

answered May 23, 2017 at 16:23

notionquest

39.4k6 gold badges120 silver badges111 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Omisha gupta · Accepted Answer · 2022-09-02 14:52:41Z

3

Make sure the prefix you're adding contains safe special characters mentioned here. As per AWS documentation, some characters require special handling. Please be mindful of that.

Also, I noticed modifying the trigger on lambda page doesn't get applied until you delete the trigger and new one (even if it is same). Learned hard way. AWS does behaves weird sometime.

answered Sep 2, 2022 at 14:52

Omisha gupta

1411 silver badge7 bronze badges

Comments

0xCursor · Accepted Answer · 2018-07-23 07:15:43Z

1

Check the prefix in bucket/properties. If there is a world like foo/, that means that only the objects inside the foo folder will trigger the evert to lambda.

edited Jul 23, 2018 at 7:15

0xCursor

2,2784 gold badges18 silver badges35 bronze badges

answered Jul 23, 2018 at 4:06

Yasser

1,3991 gold badge17 silver badges21 bronze badges

Comments

Mukesh Soni · Accepted Answer · 2023-09-05 06:29:51Z

1

I faced the same issue, The problem was with the function name itself. Try to check the value of the prefix to see if that matches perfectly with the resource.

If the resource is: resource/ and prefix is /test

then the actual folder path becomes: resource//test

just remove the '/' before test and it should work fine.

answered Sep 5, 2023 at 6:29

Mukesh Soni

1391 silver badge10 bronze badges

Comments

SKN · Accepted Answer · 2023-01-04 01:51:51Z

0

Faced similar issues and figured our that the folder names should not have spaces.

answered Jan 4, 2023 at 1:51

SKN

111 bronze badge

Comments

Jacob Joy · Accepted Answer · 2023-05-24 11:31:18Z

-1

Currently Under S3 there is option to Send notifications to Amazon EventBridge for all events in this bucket. Turn on

answered May 24, 2023 at 11:31

Jacob Joy

5566 silver badges7 bronze badges

Collectives™ on Stack Overflow

AWS Lambda function trigger on object creation in S3 does not work

6 Answers 6

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related