Re:S3 trickery: using it as a scheduler
by d_white on Friday September 14, 2018 @05:33AM
(#17985870)
I wasn't really too worried about picking apart the approach. If order mattered, you'd be looking at other approaches anyway.
Mainly just calling out a gotcha where you might quietly miss out on scheduled events with no warning.
For example:
1. Object written to successfully to bucket.
2. `s3:ObjectCreated:Put` is _never_ delivered.
The possibility of duplicate events are warned about a lot in the AWS ecosystem, and this sets up an expectation of "at-least-once" delivery.
This seems overcomplicated compared to using a regular timed event to trigger a lambda and having it decide what to execute conditionally.