[toomuchtodo]

Reduces egress costs from less steps (where you're paying for bandwidth each time you move bits), no need to manage your own lambda functions, more predictable pricing, API out of the box for variant configuration and image association, easy turn up for existing Cloudflare customers. Would expect it's trivial to CNAME a subdomain of a domain you own to their own white label domain for this service.

[zaidf]

We plan to support custom domains (just not at launch!)

[weird-eye-issue]

You don't generally pay for bandwidth within AWS so those "extra steps" wouldn't factor in to the costs

[toomuchtodo]

I admit it has been a while since I've been familiar with specific internal AWS bandwidth costs (cost for transfers between AZs, for example), so my apologies if that was too broad of a stroke (I am familiar with AWS pricing "gotchas" where you incur unexpected costs with services). In any case, Cloudflare does not charge for bandwidth with this product. Cloudfront's egress pricing can be found here [1].

Depending on your use case (from an image hosting & CDN perspective), this product is a slam dunk vs rolling your own on AWS.

[1] https://aws.amazon.com/cloudfront/pricing/

[weird-eye-issue]

Yeah I'd agree