I don't really take issue with running this on AWS Lambda. Seems as good a place as any. You're right that there are other straightforward options, but they do

I don't really take issue with running this on AWS Lambda. Seems as good a place as any. You're right that there are other straightforward options, but they do have downsides. Worst case is you have mismatch of workloads (e.g. a rogue cronjob affecting another service). Or you end up with resources that are largely idle. That said, I agree with your unease on the application side. If you had a dozen (or many dozen) of these you've got pieces and parcels of logic all over the place. I think some architecture/style changes could be mitigations here. A shared library might be one.