title: Lambda triggers for DynamoDB changes
body: <p>I'm planning on changing my service from using SQS as temporary storage that trigger lambdas to process the data to using DynamoDB for more permanent storage.</p>
  
  <p>DynamoDB offers a trigger for each row change which can also be batched together which is great. But it will also trigger on Deletes, which is something that I do not want as that could trigger 1000 lambdas which nothing to do. 
  Is there a way to disable triggering on Deletes and only listen to Insert and Modify?</p>
  
  <p>Another approach that I’ve been thinking about is to have another lambda query the database for new changes and then launch lambdas based on the changed input. For this approach I'm a bit unsure what the best way to trigger the lambdas are to get more concurrent executions, I'm afraid that if i trigger the lambdas for each change that I would hit the lambda execution ceiling. </p>
  
  <p>Pushing it to SQS and having that trigger the lambda should work, but is there a way to do this without sqs?</p>