Why should one use Amazon SES when emails can be sent using existing SMTP?
and that requires a form submitted via root credentials (IAM identity will not work)
I had success in that just opening a case (with premium support in one occasion but also with account/billing in another)
More on reddit.comI Caved and switched to Amazon SES to send my emails
Amazon SES - is it hopeless for me?
You have your DKIM Signature in your DNS?
More on reddit.comAWS Simple Email Service (SES)
What email tools does Amazon SES offer?
Can Amazon SES send emails with attachments?
What prevents Amazon SES users from sending spam?
Videos
I'm writing a microservice that picks up an email address from the database (or a bunch of email addresses at times) and send them an email about updates related to the service.
I'm looking if Amazon's SES will help me complete my goal. But as my work is progressing, I'm questions related to why should I use SES for sending email? Can I not achieve the same by using my G Suite's email service and send an email using SMTP?
Please help. Why should I use Amazon SES?
-
EC2 throttles port 25
-
Amazon IPs are blacklisted for emailing everywhere except for SES range
-
Higher throughput than regular opensource MTA
-
Bounce and complaint management
To be honest, if your needs are quite low, using GSuite is going to be just fine.
Make sure to set up SPF/DKIM/DMARC and most providers will accept your mail with no issues.
If you have bigger needs (multiple millions) start looking into Mailchimp/Sendinblue etc...
Why should I use Amazon SES?
If you want to 100% control your own email service (and not route it thru yet-another-cloud), but still not pay for a server 24x7.
Also, coupling your internal email to your product email could cause problems down the road. (I.e. what if you move your internal mail off of GSuite?)