jams2018
commented
5 years ago Three Lambda functions have been created as requested.
ad440-w19-lambda-crawler-prod1 ad440-w19-lambda-crawler-prod2 ad440-w19-lambda-crawler-prod3
Open mrvirus9898 opened 5 years ago
jams2018
commented
5 years ago Three Lambda functions have been created as requested.
ad440-w19-lambda-crawler-prod1 ad440-w19-lambda-crawler-prod2 ad440-w19-lambda-crawler-prod3
mrvirus9898
commented
5 years ago Estimated time: 4 hours
Time Spent: 8 hours
This turned into quite the odyssey. There were many bugs written up, and a lot of solid work from everyone in the Crawler Crew and DevOps. Deployment bugs were identified and most were resolved. This issue has not been fully resolved and implemented do to some on going issues, however the work done with this issue did support Crawler Crew and helped make a better product.
mrvirus9898
commented
5 years ago Related to bug #88 #83 #76 #75
mrvirus9898
commented
5 years ago 
Currently, our lambdas, logs, triggers, and such are scattered across several accounts and environments. This is unacceptable for our production environment, so ensure that lambda functions are prepared (but not deployed) and set up triggers for those lambdas.
Then, write a simple python script that enables the team to roll out these triggers without having to deal with the clumsy AWS dashboard.
Please indicate the time spent on this, any issues that you are having, any good references you found for this subject, and credit anyone helped you out.
Related to #69