AWS Lambda : creating the trigger

Question

When I try to add the trigger, I get the following error:

"There was an error creating the trigger: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type."

I'm not sure what's gone wrong here.

Did you created a trigger with the same name earlier and used it somewhere and then delete that trigger, and now creating trigger with the same name? This kind of problem happens when the previously created trigger is still "linked". Also you can check the AWS forms here — Jinesh Shah
– Jinesh Shah, Commented Sep 8, 2017 at 4:58
Please tell us more about what you were doing. What type of trigger? What values did you select? Do you have any other Lambda functions with triggers defined? — John Rotenstein
– John Rotenstein, Commented Sep 8, 2017 at 7:40
One reason could be that some other lambda function previously using the same trigger was deleted. What is the trigger you are using to invoke Lambda? — Vijayanath Viswanathan
– Vijayanath Viswanathan, Commented Sep 8, 2017 at 8:38

Vijayanath Viswanathan · Accepted Answer · 2017-09-12 11:34:41Z

7

One reason could be that some other lambda function previously using the same trigger was deleted. This does not automatically clear the event notification from the S3 side. You have to navigate to the S3 console and manually delete the stale event notifications. Once that is done, you should be able to create the same trigger again for another lambda function.

answered Sep 12, 2017 at 11:34

Vijayanath Viswanathan

8,6713 gold badges31 silver badges50 bronze badges

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

Comments

anilam · Accepted Answer · 2019-12-19 12:27:36Z

6

Navigate to S3 and click on the name of your bucket.
Click on the “Properties” tab.
Scroll down to the Advanced properties and on the events section you should see 1 or more active notifications.
Click on the square to edit notifications and delete the notification that is still listening to your lambda function in error.

Congrats, no more dangling reference!

edited Dec 19, 2019 at 12:27

answered Dec 19, 2019 at 12:21

anilam

93211 silver badges7 bronze badges

2 Comments

null Nov 22, 2024 at 23:51

Yep, that's exactly what happened to me! It worked after I deleted some of the event notifications from the S3 bucket. Thanks!

Rooster242 Dec 19, 2024 at 23:55

No "Properties" tab in 2024. Can't find Advanced properties.

Collectives™ on Stack Overflow

AWS Lambda : creating the trigger

2 Answers 2

Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related