I&#x27;ve heard some bad things about Kinesis in general.  Why not have your cron job just put the logs onto S3 directly?<p>I&#x27;ve used Lambda a bit.  The debugging process can be a pain, since you&#x27;re forced the upload a ZIP file, and if your code times out Lambda doesn&#x27;t give you any traceback to indicate what happened.  There&#x27;s also a maximum run time of each Lambda invocation, which I believe is 5 minutes.  Is there a chance your parsing may run longer than that?  Also, what will you do if you upload some bad code and the parsing fails?  Will it be the end of the world if you lose data while you fix the parsing?<p>Oh, I see you plan on doing map-reduce to re-parse the logs, so maybe that part isn&#x27;t as big a deal.<p>You could also consider doing something like rsyslog -&gt; db-of-choice while also rotating the files off to S3 for long-term map-reduces.  This is all to ignore the obvious ELK cluster solution, which will give you good data visualization and investigation options, but may be more of a headache to set up and maintain than you are looking for.<p>Anyway, those are my thoughts.  Hope they help.