AWS Lambda: Error Creating Event Source Mapping: Configuration ambiguously defined

Question

An error occurred while creating the event source mapping: The configuration is ambiguous. You cannot have overlapping suffixes in two rules if the prefixes overlap for the same type of event.

I created the event earlier from the GUI console 6-7 days ago, and it worked fine. The next day, the event is simply absent, I do not see it anymore on the graphical interface of the Lambda console. But all S3 objects still seem to launch a lambda function is not a problem. If I do not see, this is not good; So I deleted the lambda function, waited 5-10 seconds before creating a new function. And now, I get the same thing above when I try to create event sources like this:

When I click "Submit", the event source tab says "You do not have event sources for this function," Lambda does not start; this means that the entire application stream is now broken :(

The problem is almost the same: " https://forums.aws.amazon.com/thread.jspa?messageID=670712 򣯸" But for some reason I can not answer this thread, so I created a new one here instead. Does anyone encounter this problem?

Actually, I am trying to answer an existing AWS forum forum: https://forums.aws.amazon.com/thread.jspa?messageID=670712򣯸 but I continue to get this ridiculous error: "Your message quota has been reached. Please try again later". And I haven’t even published anything, how can I use my quota?

Answer 1

I suspect your S3 bucket may still be "tied" to the lambda function.

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

Answer 2

The problem should be that the s3 bucket is already associated with the suffix / prefix you are trying to link. Delete the link in S3 and try again.

Answer 3

Here is a link to a YouTube video that talks about this issue and demonstrates a solution: https://www.youtube.com/watch?v=1Tfmc9nEtbU

Just like Ridwan Manuel, you must delete events by going to S3 bucket-> properties-> Events, as shown in the video.

Steps to reproduce this problem:

1. Create a bucket and create a folder named "example /"
2. Create lambda function
3. Add S3 trigger to lambda using bucket from (1) with default settings
4. Save trigger
5. Click Save and notice the error.
6. Refresh the page and note that the triggers are gone
7. Add the same segment again and notice the ambiguous link error.