title: AWS Lambda SQS Trigger not firing after queue recreation
body: <p>I've been using terraform to define some SNS topics and then SQS queues to subscribe to them, these queues then have lambdas that are triggered by SQS and pick up the messages from those queues.</p>
  
  <p>Terraform handles the creation of SNS topics, SQS queues and the policies that allows SNS to write message to the queue. The lambdas are deployed separately via the serverless CLI tool.</p>
  
  <p>All of this seems to work fine when I ran terraform first, and then deployed the lambdas. However, I had some issues with something I'd done in terraform so I decided to pull down the entire infrastructure and have it recreated, which again seemed to work fine.</p>
  
  <p>Looking at the lambdas, which never got removed, they still had the link to the queue displaying in the portal as I'd expect. If I went to the new SQS queue I could see it list the lambda correctly listed in the 'Lambda Triggers' tab.</p>
  
  <p>The problem though was that no messages were being picked up, I could see them all accumulating in the queues. The only way I found to unblock the issue was to go into each lambda, select the SQS queue and toggle them all to 'disabled', and then to 'enabled' again. At this point they all started processing the messages that had been sat in the queues.</p>
  
  <p>Has anyone else experienced this? Is there a better way of getting them to 're-associate' with the queues correctly when they are re-created?</p>