title: AWS Lambda - Deleting Recurring Failed Events From Lambda Queue
body: <p>So I have an few AWS lambda functions that are triggered by DynamoDB streams.  I've used the 'configure test' functionality a few times, and I've triggered the function myself by just adding dummy data manually to the DynamoDB table.</p>
  <p>My problem is that now I've got working code, but because I inserted test data that was wrong in the first place (doesn't match the look of the actual event data as it streams in), <strong>every time I update a table, or the lambda function itself, it won't process other events because it gets hung up on my old, bad, test data.</strong>  As a lesser problem, it's cluttering up CloudWatch.</p>
  <p>In theory, I could change my Lambda functions so that they DON'T work with actual data, and only work with my bad test data, and then once my real data starts showing up I could then switch my Lambda function back to normal, but I feel like there has to be a better way to do this that I'm just unaware of.</p>
  <p>So I'm wondering if there is any way to:</p>
  <h1>1 - look at the queue of events that have failed in Lambda and are waiting to be re-processed?</h1>
  <h1>2 - delete specific events that are in that queue so that they are NOT reprocessed by Lambda?</h1>