-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for S3:Events Prefix and Suffix Rules #27
Comments
Hi @malcyL |
Hi @malcyL |
Hi @ar90n I've tested your new release this morning and it's working as expected. The lambda is triggered when the file is first created and the key matches the rules. After processing when we change the key of the file, the lambda is no longer triggered because the new key doesn't match the rules. I've also tested with multiple lambda's all working with different prefixes. i.e. Lambda 1 processing files from I'm happy for this issue to be closed, but I'll leave it for you to do. Thank you so much for turning this feature request around so quickly. That's very impressive. |
@malcyL |
hello, having same problem in latest version 0.5.4, look like the issue is back ! |
Serverless allows for the setting of prefix and suffix rules on S3 Events:
https://serverless.com/framework/docs/providers/aws/events/s3#setting-filter-rules
I think serverless-s3-local is ignoring these rules?
My use case is an existing system which changes the key of a file after it's completed processing. For example, a file is uploaded to s3 with a bucket and key:
s3://mybucket/incoming/file1.zip
and then after processing it is moved tos3://mybucket/processed/file1.zip
.When running locally with serverless-s3-local the handler is triggered twice, once when it is initially created and again when the key is changed. When deployed to AWS this doesn't happen as the prefix and suffix rules are applied.
The text was updated successfully, but these errors were encountered: