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),…
$0.10
for emails after the first 1,000
AWS Lambda
Score 8.4 out of 10
N/A
AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
Pricing
Amazon Simple Email Service (SES)
AWS Lambda
Editions & Modules
Sending Emails from an Application Hosted in Amazon EC2
$0.10 ($0.12)
for every 1,000 emails after 62,000 (for each GB of storage)
Sending Emails from Another Email Client or Software Package
$0.10 ($0.12)
for every 1,000 emails (for each GB of storage)
Receiving Email
$0.10
for emails after the first 1,000
Sending Emails from an Application Hosted in Amazon EC2
Free
for first 62,000 emails
Receiving Email
Free
for the first 1,000 emails
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Offerings
Pricing Offerings
Amazon SES
AWS Lambda
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Simple Email Service (SES)
AWS Lambda
Considered Both Products
Amazon SES
No answer on this topic
AWS Lambda
Verified User
Engineer
Chose AWS Lambda
These are all AWS sister products, so I wouldn't say they are competitors but tools in the same box. They all work quite well together and I would say combined they are greater than the sum of their parts. Cloudformation (and SAM) templates make tying them together pretty …
Amazon Simple Email Service comes with the bundle of Amazon Web Services (AWS) and it also offers a limited number of emails per month for free. One who has a technical background and wants to send custom emails with custom domains in a professional way can go with Amazon Simple Email Service. If you have no technical background or tech team, it might not be useful for you.
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
As compare to other vendors that I have integrated response is very quick.
You can verify both domain or email to send out the emails from.
While setup you can easily configure it with your domain with few clicks like adding CNAME, DKIM records
Easy to use with or without access key and secret key within aws servers. You can directly map permissions to servers to go without credentials using boto3.
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.
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
We did not have the need of contacting Amazon for support. The documentation they provide is of great quality. Examples are easy to follow. One thing to have into consideration is we didn't have the premium support for AWS, so I can't provide details on how good or bad this service is, but in general, the basic support I had was great.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
Mailchimp has a fixed monthly price, and with the number of emails that we sent, it's pretty expensive. Since our mailings are quite infrequent, using Mailchimp didn't make financial sense for us, even though Mailchimp is a more polished, packaged solution for email marketing. We evaluated other email delivery solutions as well and didn't find anything that matches Amazon SES on reliability and pricing.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
