3 ms·
Hey zokier. Thanks for the comment. In theory yes. I could provision a new function with an exact cron schedule to run once and then tear itself down. In prac
by davidwells 10y ago
Hey zokier. Thanks for the comment.
In theory yes. I could provision a new function with an exact cron schedule to run once and then tear itself down.
In practice, this is a lot of extra logic to write to achieve this and would also potentially make own AWS account rather messy.
The hourly cron runs about 720 times a month which is far below the 1,000,000 free invocations that lambda provides under their free tier.
- gbrits 10y agoHow about using the new AWS Step Functions instead? This would allow a full push model while still keeping a nice and tight workflow: 1. fire off AWS Step function on new post to S3 bucket 2. read delay / schedule time in metadata from (assumable) markdown post 3. trigger AWS Step Function using the Wait State defined based on read value from 2. 4. As part of Step Function: After Wait State -> Execute Lambda to publish post. Note: 3) requires setting variable time in Wait State based on environment. Haven't read up so don't know if that's possible, but guess it should be.
- 101km 10y agoThis is the correct answer.
- davidwells 10y agoHey gbrits. Thanks for the comment. This looks like a great alternative solution! Haven't messed around with step functions yet but was looking into it today after I found this https://www.youtube.com/watch?v=9MKL5Jr2zZ4&t=226s https://www.youtube.com/watch?v=9MKL5Jr2zZ4&t=226s Are you using step functions for other flows?