AWS Lambda: error creating the event source mapping: Configuration is ambiguously defined

Question

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

I created an event earlier from the GUI console 6-7 days ago and it was working fine. The next day the event just missing, i cant see it anymore at the Lambda console GUI. But every S3 objects still seems triggering the lambda function not a problem. If i cant see, it is not good; So i deleted the Lambda function, waited for 5-10 seconds before creating another new function. And now, i receive the same above when i try to create the event sources like this:

When i click "Submit" the event sources tab says "You do not have any event sources for this function", Lambda does not get triggered; it means the entire application flow is now broken :(

The problem is almost the same as: "https://forums.aws.amazon.com/thread.jspa?messageID=670712򣯸" But somehow i cant reply to that thread, so i created a new thread here instead. anyone encounter this issue?

In fact, i try to response to the existing AWS forum thread: https://forums.aws.amazon.com/thread.jspa?messageID=670712&#670712 but i keep getting this funny error: "Your message quota has been reached. Please try again later.". And i wasnt even posting anything, how can i use up my quota?

Solution 1

What I suspect is your S3 bucket may still be "linked" to the lambda function.

Maybe check your S3 bucket for events and remove them there, then try creating the lambda events again? i.e. S3 bucket-> properties-> Events

Solution 2

The issue must be that the s3 bucket is already linked with the suffix/prefix you are trying to link. Remove the link in S3 and try again.

Comments

[Mestre San]

Impossible to just guess how to solve that problem. The error message is really not helpful on the Amazon Lambda console. Thanks @Ridwaan-Manuel

[Ratan Uday Kumar]

you can give suggestion in comments

[Melebius]

@RatanUdayKumar Not with the reputation of 1. stackoverflow.com/help/privileges/comment

[Ratan Uday Kumar]

given you reputation

[Stephen]

When I deleted a lambda function, it didn't delete the trigger for whatever reason causing this bug..

[panza]

This is correct, it will keep failing unless you delete the notification for that event from S3 bucket-> properties-> Events. This is definitively the correct answer.

[Cristian]

It workied for me. I went there and I removed linked events

[mewc]

Yes! Trigger wasn't showing in designer, but in S3. Removed with this method and can instantly re-attach trigger. I thought it was an issue deploying a Template twice with similar names (Cf1 vs. CF1) by accident.