$45/mo would be the minimum payment, assuming the free limit announced today actually lasted. Let's say they begin crying 12 months from now and knock it down even by 50%, now you're looking at $810 minimum per year per client site. Multiply that up by, say, 1000 sites, and you're starting to look at a "free" service that might completely pay for its own development within a year or two.
That has historically not been the direction AWS prices go, but as I mention in my other comment, itβs trivial to move if AWS tries to put you over a barrel. Object storage is a commodity, and Docker images are objects, so shrug. It would be cool if Cloudflare supported container registry primitives backed by user provided Backblaze B2 bucket config info, for example (maybe you can do this with workers?).
Properly parameterize your build/CI scripts (in this case, your container registry host and how to auth against it) for portability. Portability is your insurance against poor service provider behavior.
Sure, but say your engineers cost you $100/hr, and every hour beyond 2,000hrs per year they work, they become more unhappy.
I think it's worth spending the 8 hours/yr/site, supposing you have relatively few sites. Plus, your engineers for 1hr/month will never achieve the same SLAs that AMZN will.
For smallish numbers of sites, it seems like the AMZN solution is fine. For bigger ones, there is always enterprise pricing :-)
