Amazon Web Services (AWS) is a subsidiary of Amazon that provides on-demand cloud computing services. With over 165 services offered, AWS services can provide users with a comprehensive suite of infrastructure and computing building blocks and tools.
$100
per month
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 Web Services
AWS Elastic Beanstalk
Editions & Modules
Free Tier
$0
per month
Basic Environment
$100 - $200
per month
Intermediate Environment
$250 - $600
per month
Advanced Environment
$600-$2500
per month
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Offerings
Pricing Offerings
Amazon Web Services
AWS Elastic Beanstalk
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
AWS allows a “save when you commit” option that offers lower prices when you sign up for a 1- or 3- year term that includes an AWS service or category of services.
We recommend AWS Lightsail with Plesk Ubuntu Web Admin (free) edition for launching WordPress websites. Pricing starts with 3.5$ per month and they are providing 3 months free. In order to access advanced features of Plesk, consider upgrading to paid Plesk plans that starts with 13.50$ per month (10 websites supported). Up to 40% discount is available for the first year. Anyway, even the free Plesk Web Admin version is by itself self sufficient with free SSL.
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.
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.
If there is one thing I think AWS needs improvement on, it is the administration dashboard. It can be a nightmare to use especially when trying to access billing. This could be made better, honestly, as there should be a simplified way to access simple admin features.
While AWS was fairly easy to integrate into our solutions, it is not as easy to use without some IT knowledge. The dashboards are complicated and designed for someone who is computer savvy. If you are just want to keep track of billing, for example, you may need to take a course or spend a few hours with someone being walked through the admin console.
AWS does tend to be slow at times. If you do not have a fast internet connection, it can take time to access services that are hosted on AWS. This is not always the case but we have had clients complain about this if they are trying to access a service from multiple points (IP addresses). The only real fix we found was to make our files cache to another server and only keep current data accessible to clients.
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.
We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.
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.
Our cloud platform architecture was designed in order to collect, analyze, and optimize modern networks, from AWS-powered computing, networking, storage, and more. So, we needed a reliable, scalable, and secure global computing infrastructure. Auto Scaling and Elastic Load Balancing were key features in our evaluation and later on for scalability and high performance. We being a cybersecurity company, we needed to ensure that our cloud provider utilizes an end-to-end approach to secure and harden the infrastructure, including physical, operational, and software measures - which AWS had all in place.
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.
AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to immediately search for their compatible software's and also to guide them in a good direction. Moreover, this product is a good suggestion for every type of company because of its affordability and ease of use.
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.
Amazon Web Services is well suited when we have a huge amount of data to store, process, manipulate and get meaningful information out of. It is also suitable when we need very fast data retrieval from the database. They provide a superior product at a fair price which allows us to further our goals and push the limits of what we are capable of as a team / company.
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.
