I tried it writing a trivial python script that called a webservice every 5 minutes and stored the .json response in S3. Advantages: - Cheaper than having you

I tried it writing a trivial python script that called a webservice every 5 minutes and stored the .json response in S3. Advantages: - Cheaper than having your own micro.t1 server and setting crontab. - I have information about how much time it takes to actually run the script. Findings: - Test & debug: inside lambda only. Didn't like this, but for trivial stuff like mine it worked. - "Crontab-like" granularity: you cannot trigger a lambda function every X seconds. The minumum is a cloudwatch periodical "cron-like" trigger. - The script took much more execution time than I thought. It also required less memory, but this is not a problem ;-). - Every line you print() to stdout goes to a Cloudwatch log. It's both helpful and something to care about because Cwatch is not free.