Hi Kelly:
FWIW, I have been a user (professionally) of AWS for years, some EC2 and some LS, lots of S3 and Route 53.
I had spun up a Lightsail instance for my use as a sologig site / SOHO and after getting DNS (Route 53), Plesk, Wordpress, and SSL including DMARC, SPF, and DKIM, I spent hours trying to figure out why OUTBOUND messages weren’t being delivered. It took time to troubleshoot. Even though I had the LS and LINUX FW policies set to allow SMTP 25 (and 587) in and out, it was clear that some other policy was blocking outbound 25. (incoming was fine).
I stumbled upon a form after searching GOOGLE for help that SMTP was blocked by default, and that users could fill out this form and state their case for opening port 25.
I did so, explaining that as an expert in mail security, I was taking all prudent steps to ensure valid, proper use of outbound messaging for my site (Wordpress), my plesk (for notifications / alerts), and for a single mailbox (info@mydomain.com) for use to communicate my clients, including rate limiting of SMTP settings.
I got an autoresponder back telling me to use Amazon SES (which is great for the Wordpress part of the issue), but did not allow me to host a single mailbox on my instance. My option was to go pay for a mailhosting company or to simply move to another VPS…which I did.
So, I’ve moved on. I’m now happily on Digital Ocean who has been great with support, usability, etc.
I’m pretty much done with AWS for my own personal / professional use. If I have clients who desire to use it, I will continue to support them. But I’m jaded now re: AWS, and on the up side, I’m incredibly happy with my experiences so far with DO. I certainly won’t be electing to use the AWS ecosystem any time soon.
BUt I’m a nobody and Jeff Bezos’s pocket book certainly isn’t going to hurt from my decision to go elsewhere.