We have …
- To provide auto-response of "Contact Us" like inquiry
- We use …
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Amazon SES, and make your voice heard!
Sending Emails from an Application Hosted in Amazon EC2
Sending Emails from Another Email Client or Software Package
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Amazon Simple Email Service (Amazon SES) is an outbound-only email-sending service useful for marketing and transactional email, relying on the infrastructure of Amazon. Amazon SES provides the requisite statistics and built-in notifications for bounces, complaints, and deliveries for optimization of campaigns. Emails are sent via SMTP or the Amazon SES API.
Amazon's pricing is per usage, presently at $.10 per thousand sends. The service is free for users of Amazon EC2 (up to 62,000 messages), and for new users of the Amazon AWS service free usage tier (from the 15 GB of data transfer across AWS services).
- It has fair pricing, we do not have to loose our pockets just to send emails.
- We can customize the emails according to our choice and set the default responses to senders.
- It offers good reputed IPs, so generally our emails don't directly jump to the spam folder.
- It would be great if they could help us to track the deliveries of the emails sent via SES.
- For beginners, setting up Amazon Simple Email Service for the first time might be a little difficult task.
- Might not that be good for a non-tech savvy person.
- It very cheap in cost.
- it provide efficient monitoring for the quotas of our email limits.
- It is very easy to configure set up and handle.
- It is only hard when we need sandbox environment to setup because it is only provide on valid cases.
- Deliverability reports
- DKIM and Dmarc integration
- Ease of integration with non-Amazon infrastructure
- SES handles sending email really well, but receiving email part is very bare-bones. It can forward to HTTP endpoints, but cannot provide industry standard APIs like IMAP.
- Sends out email notifications
- Pay as you use
- Cannot send emails to unregistered users
- Reporting section is weak
- Amazon Simple Email Service is a much lower cost than most other solutions and truly makes cost a non-factor in most situations where we consider implementing it.
- The API is so well documented that implementing Amazon Simple Email Service in nearly any application or codebase is achievable with basic coding knowledge.
- While the service limits are one of the main points that keep the delivery metrics so reliable, it can be stressful to get a new implementation out the door quickly.
- If you're looking for a point-and-click style email delivery tool, this is not the right type of product for you. Amazon Simple Email Service is for a developer-centric approach to implementation into existing applications, processes, and services.
- High percentage of deliverability.
- Cost savings.
- They could have a list of bounced emails so it's easy for the sender to delete those emails from databases.
- If you're running your applications in a EC2, the first 62,000 emails are free.
- Pay as you go is a great feature.
- No cons! Great service and and easy to use.
We have used SES with several customers for the past 8 or so years.
SES solves one of the most common annoyances in programming. Email deliverability. With SES (configured correctly) we have no issues with spam filters.
- SES is highly reliable. Haven't had any issues that I know of.
- It is extremely cost effective. Most of the time we stay under the free tier which is nice!
- Once set up, it's pretty much hands free. Haven't had to adjust old code... ever.
- As with most AWS services, you're on your own unless you pay for support. So there is a learning curve, but nothing major.
- Although things may have changed, I haven't seen any email templates. Again, that may have changed.
I probably wouldn't use SES for a smaller temporary use case. There is configuration needed with SES and potential (tiny) costs.
Generally, I have one configuration that I use for most forms unless I expect high traffic. In that case I keep it separate.
- Speedy delivery - usually in seconds
- Easy setup - just a few minutes per domain
- Inexpensive to use - few dollars a month for reliable service
- The set-up interface could be made simpler. Some things aren't intuitive.
- It's not easy to find from the AWS menus.
- A simple testing script would be nice, but I've never had trouble using it.
- No SMTP server setup if already in AWS ecosystem
- Quick and Easy setup & integration
- Pay as you use - no extra cost
- Always verifies the email before you can it. Hectic process.
- Email template facility is not available.
- To provide auto-response of "Contact Us" like inquiry
- We use SES in our CI and CD pipelines to supply the necessary information to respective stakeholders about build, deployment and unit testing
- Some of the web solutions which we have hosted and requires to send outbound emails, we use SES
- It provides a Console approach to send emails. This approach is really effective to monitor your mailing activities.
- Amazon provides great integration with other services as well. One can trigger a lambda function when Email is received. One can set SNS for the notification of bounced emails.
- The HTML content as an email body makes it possible to format your email. To put the tables and bit complex layout are also easy with SES in place.
- Even if you do not want to spam, you cant send an email to the unverified users.
- Integration with other services is a bit tricky. To watch the trail, handle bounced emails, save emails on S3 are not straightforward to implement.
- When you want to send a lot of emails (in bulk), it takes a significant amount of time.
If you are not an Amazon shop and just looking for SMTP solutions, SES is not for you.
- It provides a simple syntax to create templates for customized emails
- It has a great rate limit once moved out of the sandbox
- Nice mechanisms to handle bounce and replies
- The AWS console needs to provide a GUI to create a template for an email rather than developers having to use the CLI or SDKs
- The initial sandbox limits are too low for any production application
It is less appropriate for just sending out notification emails in which case SNS should be used.
- Great pricing
- Amazing performance when accessed from inside AWS
- Granular API provides great amounts of flexibility
- Improve performance when accessed from outside AWS
- Improve web interface capabilities
- Higher deliverability
- Higher reputation
- Easy setup
- SES knowledge to setup
- Email marketing background to keep the lists with very low bounces and complaints
- suppression list removal is a pain and you can't see which emails are suppressed like with other services
- API isn't the easiest to use when integrating with PERL
- SES gets blocked by a lot of ISPs due to many bad actors using it. Having a dedicated IP is the only way to go
- Low cost; I do not know anyone that can match their low cost unless you are in the free tier of G-Suite for work Gmail.
- High reliability - messages do get delivered. We have had no issues.
- Easy to set up the basics - generate the credentials and add it to your code.
- Setting up for bounces is just so hard! Amazon needs to do a better job here in providing instructions.
- Struggling to set up spf- again, the instructions are not great and often confusing.
- Easy to send thousands of messages without worrying about scaling.
- Very easy to understand SDK and modules in Java and Python and start sending custom emails in minutes.
- Not a costly service. Implementing using the service and training people is really simple.
- Could maintain a dashboard with the list of previously sent emails and their templates.
- Amazon Simple Email Service dashboard could be made more user-friendly by including few HTML snippets so that they are readily available for testing.
- Setup was easy. It does require proof of domain control as well as a human review, but while those items are pending you are able to fully set up the system to be able to run once approval is done and not have to bounce between development and production configurations.
- SES does not seem to have any major issues at the moment, it's an email relay service and it does that job swimmingly.
- Amazon SES is a simple service that's not bloated with unnecessary features.
- It's fast and reliable. You can literally send thousands of emails without any issue.
- 10 cents for 1000 emails? The price is just simply amazing!
- It could be more user-friendly for non-tech-savvy people.
- I've praised that it does not have any unnecessary features. However, some people could use implemented tools.
- Initial limit is too low but you can lift it with no issues.
Speaking about features that are lacking; if you do not have software to send and track all the subscriptions, you may want to look into services that have that implemented already. Personally, I'm using Amazon SES as my SMTP server and Sendy to track all the subscriptions, statistics, reports and all the other features. The price difference between putting several products together and using all-in-one product is huge. Therefore, hands down to Amazon SES for [being] such a great product.
- Very high send rates. We often send out over 50,000 emails in a matter of minutes (30-40 minutes).
- Very simple to authorize email sending from an entire domain.
- You get full control of your emails and are not as strictly bound to a set of policies as you would be with an email "platform" like MailChimp. Of course, that means you have to do more legwork too.
- You cannot send embedded images (Base64 encoded) in your emails. This is a pretty big gotcha. So if you want to send images along, it's best to store them externally.
- Virtually zero analytics on your emails. It is up to you to implement open detection, click detection etc.
- Has no email list storage. That's up to you.
In addition to its simplicity, the dirt-cheap pricing is almost negligible. The monthly bill for all of our e-mails is roughly $4 per month, and simply cannot be beat by any other SMTP provider.
- DKIM signing for all messages. This absolutely maximizes the probability of a message reaching a user's inbox, and not the spam folder.
- API *and* SMTP access, making it possible to connect any system to SES. No matter what programming language or what server, there is always a library for sending e-mail messages that is compatible with SES.
- SES makes it trivial to send thousands of e-mails from known mail servers. No longer do you have to worry about your server's IP address being blacklisted because it originated too many e-mails.
- Incredible credential management for increased security. With IAM, you can create API keys (or SMTP credentials) for each individual piece of an infrastructure, making debugging very easy.
- For users that are not used to semi-complex APIs, the AWS SDK can be a little intimidating. That said, with the SMTP credential feature, the API learning curve can be avoided.
- It is frustrating that you have to verify each e-mail address or domain name (wildcard) you wish to use in the From: header of the e-mail messages. I understand this is a security feature, but for long-time verified accounts, it would be nice to use arbitrary e-mail addresses and domains.