3 ms·
Finally. My two production projects are built entirely on Cloudflare workers platform, and I dread every time I have to login into AWS to manage SES. I even wro
by freetonik 1y ago
Finally. My two production projects are built entirely on Cloudflare workers platform, and I dread every time I have to login into AWS to manage SES. I even wrote a note for myself with instructions which buttons to press and where to navigate, like you'd write for your elderly relative who's "not good with technology".
- aprilnya 1y agoHonestly this is why I like what Cloudflare is building nowadays. They aren’t just a CDN but rather they’re becoming a full on cloud, like AWS and Azure are - except their developer experience is just so incredibly better than any other cloud
- SahAssar 1y agoMy experience is pretty much the opposite. Bad support for common APIs like S3, terrible support for terraform/opentofu, none/lackluster help in support or github issues.
- aetherspawn 1y agoOne thing I like about Cloudflare is that each product makes sense on its own, not like AWS: go make access policies in one place, ACLs in another, and before you know it you have no idea how anything works without taking an AWS Certified Consultant course. Cloudflare feels like separate silos, each individually complete and usable. And the “minimum viable path to make-this-work” is usually 1-2 button presses, rather than filling in pages and pages of configs. I also love that Cloudflare is scoped under each domain, it helps keep my projects separate.
- Manouchehri 1y agoI documented the process of using AWS SES from a Cloudflare Worker about a year ago. https://www.ai.moda/en/blog/ses-emails-from-workers https://www.ai.moda/en/blog/ses-emails-from-workers Hopefully it’s helpful next time for you!