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
Amazon SNS
Score 8.0 out of 10
N/A
Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
Pricing
Amazon Simple Email Service (SES)
Amazon Simple Notification Service (SNS)
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
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 have used a dozen services. They are almost all more expensive. Some force you to wait one week to approve/deny your account if they suspect that the email database is not legal. I have very important clients with legal databases that were rejected by other companies and …
We really thought of using Mail Chimp, and have used it before in the past, but the advantage of Amazon Simple Email Service is that we were using AWS infrastructure for these web applications. We had the instances running in EC2, our database was an RDS and Logs Cloudwatch, so …
Although I like the email template capability with these other services, and one of them is actually a customer, the simplicity, reliability, and cost effectiveness of SES keeps it at the top of the list. Not to mention, we use so many other services at AWS, the integration is …
I'd recommend SendGrid and Mailchimp to most smaller business that can't dedicate engineers solely to their email pipeline. The price/value ration is fair and the tools are fairly flexible for the intended use cases. It's often a good idea to start to start there and only pivot …
The process of setting up Amazon was really easy and straightforward compared to Mandrill.
And right now Mandrill is an add-on in MailChimp, so no longer a real alternative.
I also use Sendgrid for sending all my transactional emails. It is more expensive than SES, but I feel it is more reliable with a better reputation than SES. I have also used Mailgun, but they are more expensive than SES and deliverability on a shared IP are as bad as SES.
In terms of ease of use, Gmail is the best. But, SES is preferred because there is no rate limit and it is so inexpensive. If you want list management, image embed capability, and easy setup, SES is not for you. You need to be technically sound and have a thorough understanding …
I've selected Amazon SES due to two factors. First of all, the price is really competitive. I haven't seen a better price and if you did, please send me an email. The second factor was that I do not need all those functions to track the subscriptions, sales, reports because I …
SES is a much lower level technical tool than the other solutions we've used in the past with the exception of Mailgun. We've found SES to actually be much easier to use than Mailgun, although not as powerful. A good way to explain the difference between Mailchimp, Constant …
Amazon SES is bare-bones, insofar as it will not "help" you with the contents of your message. You cannot use variables in the e-mail, it will not automatically track whether or not the recipient opened the mail or not, it will not help with unsubscribe links, and it will not …
They have fix cost and not pay per use model like Amazon Simple Email Service (SES) and moreover selecting best suited plan is also difficult as per our organisation use case.
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is …
I worked with Adobe campaign 2 years ago and comparatively, SNS is way better and easier to integrate with. There's a lack of latency with SNS and better customer support. Easier to group with subscriptions and easier to work from the command line with the use of the SDK. All …
SNS helps in integrating with other AWS components which are used in development such as Lambda, APIGW, S3 and DynamoDb easily. If used with third party software like PagerDuty, it makes the development and integration more complex. It is used mostly for publishing and …
Amazon Simple Notification Service and PagerDuty have been used by various organizations. Amazon SNS is ideal if you're within an AWS environment. PagerDuty is used when we are working outside of Amazon Web Services. Though PagerDuty is more expensive than Amazon SNS they do …
We have looked at other service providers, including the local service providers as well, but Amazon SNS stood ahead of all in terms of service availability across the globe and cost-effective plans per notification SMS. Moreover, we can also use Amazon SNS along with other AWS …
Common confusion between SNS and SQS. SNS directs information to its subscribers without any effort on the subscribers or individuals' end. SQS gathers the information and then the individual has to almost go find it. They do similar things but in a space where information can …
We have opted ultimately for AWS SNS once configuration was set topics and subscriptions setup. Site 24 and US Monitor are considerations to this product, but incur cost outside of Amazon, so not best for starting up for our needs.
The main reason we chose Amazon SNS is for easy integration with all the workflows in AWS. The other alternatives can be (and really are) best in specific points, but the main strength of SNS is that is one service of AWS, so we don't need to complicate things in our …
Our company prioritizes using AWS offerings unless there is a strong use case for using something within Azure. SQS is a similar service that solves different problems and we are using it in conjunction with SNS.
We use EC2 instances to train ML model against a heavy volume of data. When the model is trained (i.e. loss reduces to a certain level), we push notification to all the stakeholders to notify them the new model is available. To achieve it, SNS is the most simple and cost …
Many products, including PagerDuty, can be used to notify stakeholders when alarms are triggered. SNS is only suitable for non-emergency email alerts, and integration with CloudWatch is its only advantage. If you want to be notified of an issue by email, SNS can be configured …
SNS is much more customizable compared to SES and allows for many more delivery methods. While it is better for email-based notification services, not being able to send notifications via SMS limits your app functionality considerably. Being able to switch message delivery …
As I mentioned previously, I wish we had gone with a different service such as a Mixpanel or OneSignal as they are reputable in the space and are known for their strong support and documentation. AWS SNS was the way to go for us at the time we chose it due to the fact that we …
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.
Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.
Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)
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.
At times you receive access denied errors which are annoying.
Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
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.
The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.
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.
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.
Amazon Simple Email Service has improved delivery rates and eliminated delivery issues everywhere we have impelmented it.
We have been able to enforce stricter security within our application environments because we are using Amazon Simple Email Service instead of handling email transmissions natively.
Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
Amazon SNS usage needs prior knowledge of programming.