- 最新
- 投票最多
- 评论最多
The issue with this seems to be coming from changes to the trigger not propagating through the system. I found an answer here. The steps I now take to get the trigger to work are:
- Add the S3 Trigger event with the correct prefix
- Refresh both the Lambda page and S3 Bucket page
- In the Lambda, navigate to the Code tab and select test to run a test of the lambda function and generate a cloudwatch log.
- Check the cloudwatch logs and confirm the test run went through
Once you have done this, you can add a test file to your bucket with the prefix and confirm everything is working.
Strangely, I have been able to sometimes get the trigger to work when changing the prrefix. For instance I attempted:
"datasets/Combined/"
Which correctly triggered, but this level up allows for too many files to trigger this lambda. I adjusted back to:
"datasets/Combined/1. Raw/Demo/"
which continued to fail. I thought this may have something to do with the space in the directory "1. Raw", but when I attempted to move back to "datasets/Combined/" the trigger no longer worked. It is still unclear why this does not consistently work.