Why do I get the error "Configuration is ambiguously defined" when creating an Amazon S3 event notification to trigger my Lambda function?

Last updated: 2022-11-14

I'm trying to create an Amazon Simple Storage Service (Amazon S3) bucket event notification to trigger my AWS Lambda function. Why am I getting the error "Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type."?

Short description

The Configuration is ambiguously defined error occurs when a notification's event information and its prefix or suffix overlap with an S3 bucket's notification configuration.

The error can occur when you're doing one of the following:

  • Recreating an S3 event notification that you recently deleted.
  • Creating S3 event notifications for multiple overlapping events using overlapping prefixes or suffixes.

Note: Amazon S3 event notification configurations allow overlapping events with non-overlapping prefixes or suffixes. The configurations also allow non-overlapping events with overlapping prefixes or suffixes.

For more information and examples, see Configuring event notifications using object key name filtering.


Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.

Do either of the following:

Then, do one of the following:

Remove an overlapping event

In the Amazon S3 console, delete an existing event notification that overlaps with the new one that you're trying to create.

Note: When you delete a Lambda function trigger, the associated S3 event notification is not automatically deleted. You must also delete the notification in Amazon S3 before creating a new trigger without suffix constraints.


Update the notification configuration JSON file on your S3 bucket by running the AWS CLI command put-bucket-notification-configuration.

Reconfigure the new notification

Change the object key naming for your S3 bucket namespace to allow multiple overlapping events with non-overlapping prefixes.

For example, to specify that overlapping event objects, such as uploaded images, use a different S3 bucket folder (prefix) depending on the image file type (suffix):

  • S3://mybucket/uploadedJPEG
  • S3://mybucket/uploadedGIF

Redesign for your use case

If you can't reconfigure your S3 event notification to avoid the overlap, try redesigning your architecture to work around it.

For example:

Tip: For more complex architecture and processes, use an AWS Step Functions state machine to design and manage your workflow. For more information, see AWS Step Functions use cases and Tutorials for Step Functions.