You're suggesting we engineer something on S3 and aws-cli, while complaining about engineering something ourselves when AWS offers a perfectly good queue service that requires no engineering?
Uff. I'm going to buy a hut in the woods and live in it.
perfectly fine with using SQS, just it will have worse availability guarantees than S3 - people should understand tradeoffs
It is really hard to beat the cost/benefit ratio of S3.
a lot of mediocre engineers cannot swallow a pill that all their expensive work with hundreds of hours of overengineering could be replaced by a couple of AWS managed serverless services stitched together with a few mouse clicks or a single .yml file
sometimes it really does make sense just to pay someone else to solve the problem. not always, but not never.