What is Amazon SES?

Amazon SES eliminates the complexity and expense of building an in-house email solution or licensing, installing, and operating a third-party email service. The service integrates with other AWS services, making it easy to send emails from applications being hosted on services such as Amazon EC2.
Amazon SES is a tool in the Transactional Email category of a tech stack.

Who uses Amazon SES?

1282 companies use Amazon SES in their tech stacks, including Netflix, Intuit, and HotelTonight.

274 developers use Amazon SES.

Amazon SES Integrations

Apostle.io, Backand, Mailtrain, SignalFx, and Mattermost are some of the popular tools that integrate with Amazon SES. Here's a list of all 11 tools that integrate with Amazon SES.

Why developers like Amazon SES?

Here’s a list of reasons why companies and developers use Amazon SES
Amazon SES Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose Amazon SES in their tech stack.

Cyril Duchon-Doris
Cyril Duchon-Doris
CTO at My Job Glasses · | 9 upvotes · 5.6K views
atMy Job Glasses
Amazon CloudWatch
Amazon SNS
Amazon S3
Amazon SES
AWS Lambda

We decided to use AWS Lambda for several serverless tasks such as

  • Managing AWS backups
  • Processing emails received on Amazon SES and stored to Amazon S3 and notified via Amazon SNS, so as to push a message on our Redis so our Sidekiq Rails workers can process inbound emails
  • Pushing some relevant Amazon CloudWatch metrics and alarms to Slack
See more
Simon Bettison
Simon Bettison
Managing Director at Bettison.org Limited · | 6 upvotes · 27.6K views
atBettison.org Limited
Amazon EC2 Container Service
Amazon VPC
Amazon Route 53
Amazon SQS
Amazon SES
Amazon CloudFront
Travis CI
Amazon ElastiCache

In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

See more
Tim Joseph Dumol
Tim Joseph Dumol
Lead Software Architect at Kalibrr · | 1 upvotes · 1.4K views
Amazon SES

Our internal emails (such as exception notifications) are sent via Amazon SES, since it's cheaper than using Sendgrid. We also use Amazon SES as a fallback in case we have deliverability issues with Sendgrid. Amazon SES

See more
Kelvin Jones
Kelvin Jones
Amazon SES

Sending transactional emails, such as reminders, contact form notifications, confirmations …etc. Amazon SES

See more
Simone Marcato
Simone Marcato
Partner & CTO at Hevelop · | 1 upvotes · 1.3K views
Amazon SES

Amazon SES is the email service we commonly use in clous AWS e-commerce infrastructure. Amazon SES

See more
Philip Sahli
Philip Sahli
at sahli.net · | 1 upvotes · 1.3K views
Amazon SES

Sending reminders and alerts for failed tests oder ssl certificate expirations Amazon SES

See more

Amazon SES's features

  • Simple – Amazon SES eliminates the complexity of licensing, installing, and operating a third-party service, or building and maintaining an internally hosted email solution. Sending email through Amazon SES is as simple as using SMTP or calling an API, and Amazon SES makes it easy for you to monitor your sending activity and deliverability statistics.
  • Inexpensive – There are no up-front fees or fixed expenses with Amazon SES, and you benefit from the efficiencies of Amazon’s scale. Your only costs are low charges for the number of emails sent and data transfer fees.
  • Reliable – Amazon SES runs within Amazon’s proven network infrastructure and datacenters. All outgoing email messages are stored redundantly across multiple servers and datacenters, providing high availability and data durability.
  • Scalable – Amazon SES is based on the scalable technology used by Amazon web sites around the world to send billions of messages a year.
  • Designed for use with other Amazon Web Services – You can track your bounces and complaints in Amazon Simple Notification Service (Amazon SNS), and you can set up Easy DKIM or verify any domain you administer via Amazon Route 53 with a few clicks of your mouse. There is also a free usage tier for emails originating from Amazon EC2 and AWS Elastic Beanstalk.

Amazon SES Alternatives & Comparisons

What are some alternatives to Amazon SES?
SendGrid's cloud-based email infrastructure relieves businesses of the cost and complexity of maintaining custom email systems. SendGrid provides reliable delivery, scalability and real-time analytics along with flexible API's that make custom integration a breeze.
Mailgun is a set of powerful APIs that allow you to send, receive, track and store email effortlessly.
MailChimp helps you design email newsletters, share them on social networks, integrate with services you already use, and track your results. It's like your own personal publishing platform.
Amazon SNS
Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint.
Mandrill is a new way for apps to send transactional email. It runs on the delivery infrastructure that powers MailChimp.
See all alternatives

Amazon SES's Stats

- No public GitHub repository available -