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 Elastic Beanstalk
Score 9.0 out of 10
N/A
AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Pricing
Amazon Simple Email Service (SES)
AWS Elastic Beanstalk
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
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Public & Private Cloud Senior Business Technology Engineer
Chose AWS Elastic Beanstalk
We now default to Amazon ECS, due to flexibility this gives us with how workloads scale, and more network flexibility as many of our workloads are internal / external facing. We selected Elastic Beanstalk at beginning of our containerization phase, which suited our needs …
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.
I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -
I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
Scalability & Security comes with the service, which makes it the absolute perfect product for your business.
Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.
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.
Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
Common application architectures can be referenced as patterns during project [setup].
Multiple environments can be deployed for an application giving more flexibility for experimentation.
Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.
As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.
It is a great tool to manage your applications. You just need to write the codes, and after that with one click, your app will be online and accessible from the internet. That is a huge help for people who do not know about infrastructure or do not want to spend money on maintaining infrastructure.
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.
As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.
- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.
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.
We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.
