Adds info about lambda event source mapping issue

Author: ofhouse

README.md

@@ -268,6 +268,15 @@ So issues that exist on Vercel are likely to occur on this project too.
   After running the initial `terraform destroy` command (that failed) wait ~1 hour and run the command again.
   This time it should run successfully and delete the rest of the stack.
 
+- Initial apply fails with error message `Error: error creating Lambda Event Source Mapping` ([#138](https://github.com/dealmore/terraform-aws-next-js/issues/138))
+
+  There is some race condition when the permissions are created for the static deployment Lambda.
+  This should only happen on the first deployment.
+
+  **Workaround:**
+
+  You should be able to run`terraform apply` again and the stack creation would progreed without this error.
+
 ## License
 
 Apache-2.0 - see [LICENSE](./LICENSE) for details.

modules/statics-deploy/main.tf

@@ -199,10 +199,9 @@ module "deploy_trigger" {
       service    = "s3"
       source_arn = aws_s3_bucket.static_upload.arn
     }
-    # TODO: Check if we need this
     InvalidationQueue = {
-      service    = "sqs"
-      source_arn = aws_sqs_queue.this.arn
+      principal  = "sqs.amazonaws.com"
+      source_arn = aws_sns_topic.this.arn
     },
   }