# Error: Configuration is ambiguously defined

**URL:** <https://forum.serverless.com/t/error-configuration-is-ambiguously-defined/3777>\
**Category:** Serverless Framework\
**Created:** [February 15, 2018, 3:17pm UTC](https://forum.serverless.com/t/error-configuration-is-ambiguously-defined/3777 "2018-02-15T15:17:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bfieber](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bfieber/32/653_2.png) [@bfieber](https://forum.serverless.com/u/bfieber)\
**Post date:** [February 15, 2018, 4:26pm UTC](https://forum.serverless.com/t/error-configuration-is-ambiguously-defined/3777/2 "2018-02-15T16:26:54Z")

</div>

That’s a limitation of AWS. You can read more about it in the [AWS Docs here](https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html#notification-how-to-filtering-examples-invalid)

You could consider trying a [Messaging Fanout Pattern for Serverless Architectures Using Amazon SNS](https://aws.amazon.com/blogs/compute/messaging-fanout-pattern-for-serverless-architectures-using-amazon-sns/)

Buggy talks about it in a similar thread [HERE](http://forum.serverless.com/t/sns-possible-to-send-multiple-messages-in-one-call/2747/3)

Hope it helps.

---

_[View the full topic](https://forum.serverless.com/t/error-configuration-is-ambiguously-defined/3777)._