22 engineers on Hacker News describe using Amazon SES first-hand: 9 endorse it, 6 regret it, 2 are mixed.
“we use SES to send our emails and we use RDS for our app DB, because their performance profiles and uptime guarantees are more than acceptable”
endorse · production · scott_w · 2025-12-20 · source ↗ · wrong label?“we switched over to SES, and we had 3 dedicated IPs, and for our volume back then... this worked very well.”
endorse · production · slau · 2023-08-18 · source ↗ · wrong label?“I have set up the same thing for myself and have been using it for several years now”
endorse · personal · 3 yr · teitoklien · 2021-12-26 · source ↗ · wrong label?“We accidentally had ses credentials set up on our QA server and quickly got banned... ses is still useful for processing incoming email via Lambda”
mixed · production · statictype · 2020-01-04 · source ↗ · wrong label?“We switched to phplist + Amazon SES several years back after calculating what our MailChimp bill would be... and are glad we did.”
endorse · production · arbuge · 2018-10-09 · source ↗ · wrong label?“It wasn't uncommon for us to devote 20+ man hours per week in dealing with email issues while using AWS.”
regret · production · nothing-special · 2017-10-18 · source ↗ · wrong label?“we tried SES and had far too many emails going to our customer's SPAM folders, so we switched back”
regret · production · leftnode · 2017-10-17 · source ↗ · wrong label?“SES gave us a huge drop in mail sending cost.”
endorse · production · a2tech · 2017-10-17 · source ↗ · wrong label?“We've had quite a lot of experience using Amazon SES, as we run an email marketing platform on it. We run both our marketing and transactional emails using it”
endorse · production · 02thoeva · 2017-07-27 · source ↗ · wrong label?“consider AWS SES. It doesn't have the fancy tempting of Mandrill/Sendgrid/etc, but it's a fraction of the cost and the deliverability has been excellent.”
endorse · production · scosman · 2016-09-02 · source ↗ · wrong label?“Our emails sent through SES, often ended up in people's spam folder despite doing the requisite verifications (SPF, DKIM).”
regret · production · lyonlim · 2016-07-17 · source ↗ · wrong label?“we switched from SES to Mandrill because of delivery problems from SES.”
regret · production · aquark · 2016-03-01 · source ↗ · wrong label?“we switched to Amazon's SES service to send email and it entirely fixed the issue.”
endorse · production · shiftpgdn · 2015-03-12 · source ↗ · wrong label?“After using SES for close to two years, I'd suggest looking elsewhere if you really care about deliverability or stats/metrics.”
regret · production · 2 yr · gtaylor · 2014-03-26 · source ↗ · wrong label?“we moved off it when ~ 4,000 sends was taking 2-3 hours nightly... Still use SES for transactional stuff, though.”
mixed · production · oneeyedpigeon · 2013-11-12 · source ↗ · wrong label?“Last thing we use that I haven't seen listed is Amazon SES (email). I love the no-commitment pricing”
endorse · production · bmelton · 2012-12-22 · source ↗ · wrong label?“We switched away from Amazon SES to Mailgun for sending weekly newsletters... No more XML parsing with SES!”
regret · production · riobard · 2012-03-03 · source ↗ · wrong label?“We migrated from Zoho to SES recently hoping to fix this, but that has not helped.”
neutral · production · vishnumohandas · 2024-07-05 · source ↗ · wrong label?“We switched from using SMTP to the AWS SDK for SES because when sending an e-mail the SDK returns the unique message ID of the e-mail.”
neutral · production · chrizel · 2023-11-20 · source ↗ · wrong label?“there are plugins for running the lambdas locally as well as for dynamodb, sqs, ses and eventbridge.”
neutral · production · wdfx · 2021-12-03 · source ↗ · wrong label?“RDS (MySQL or PostgreSQL), ES (OpenDistro), S3 (Minio), and SES”
neutral · production · mozey · 2021-04-19 · source ↗ · wrong label?“I am guilty of using SES myself”
neutral · production · entropyneur · 2013-03-21 · source ↗ · wrong label?