Scheduling event on s3 bucket fails

[jesse-peters]

Context

Using zappa on python 3.6 inside a venv.

Expected Behavior

I have an s3 bucket which has a few existing event subscriptions. There is no overlap with the event subscription that zappa is trying to manage. I expect to be able to schedule a new subscription with zappa, even if there are already some on the bucket.

Actual Behavior

It looks at the bucket, and says that the event schedule already exists.

Possible Fix

I suspect it is only looking at the event types, and does not actually look at the filters when looking to see if an s3 event subscription already exists.

Steps to Reproduce

1. Add an event subscription on prefix A manually to an s3 bucket
2. Attempt to schedule zappa with an event subscription on prefix B. It should tell you that the event subscription already exists.

Your Environment

• Zappa version used: 0.45.1
• Your zappa_settings.py:

{
			"function": "app.function",
			"event_source": {
				"arn": "arn:aws:s3:::s3bucketname",
				"key_filters": [{
					"type": "prefix",
					"value": "A"
				}],
				"events": [
					"s3:ObjectCreated:*"
				]
}

[richiverse]

This is an AWS bug. See https://aws.amazon.com/blogs/compute/fanout-s3-event-notifications-to-multiple-endpoints/ for workaround until AWS either fixes it... or not.

…

On Wed, Mar 14, 2018 at 12:06 PM Jesse Peters ***@***.***> wrote: Context Using zappa on python 3.6 inside a venv. Expected Behavior I have an s3 bucket which has a few existing event subscriptions. There is no overlap with the event subscription that zappa is trying to manage. I expect to be able to schedule a new subscription with zappa, even if there are already some on the bucket. Actual Behavior It looks at the bucket, and says that the event schedule already exists. Possible Fix I suspect it is only looking at the event types, and does not actually look at the filters when looking to see if an s3 event subscription already exists. Steps to Reproduce 1. Add an event subscription on prefix A manually to an s3 bucket 2. Attempt to schedule zappa with an event subscription on prefix B. It should tell you that the event subscription already exists. Your Environment - Zappa version used: 0.45.1 - Your zappa_settings.py: { "function": "app.function", "event_source": { "arn": "arn:aws:s3:::s3bucketname", "key_filters": [{ "type": "prefix", "value": "A" }], "events": [ "s3:ObjectCreated:*" ] } — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1442>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACjB_gU1yaiIQCrdKce-ihBVbmL6vStyks5teUAAgaJpZM4SquHL> .

[jesse-peters]

I can have different prefixes hit different lambda functions if I set it up manually on the bucket though.

(those are different functions)

[scoates]

Sorry if I closed this too early. (-: reopened.

[nrowland]

I also am seeing this issue where zappa updates are deleting other pre-existing events on an s3 bucket. Is this going to be resolved any time soon?

[farridav]

*Bump this is affecting me too