Skip to main content
TrustRadius
AWS Elastic Beanstalk

AWS Elastic Beanstalk

Overview

What is AWS Elastic Beanstalk?

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).

Read more
Recent Reviews

Fantastic Tool by AWS

8 out of 10
May 09, 2021
Incentivized
AWS Elastic Beanstalk is being used in specific departments of my organization. The major business problem that it solves is that there is …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 11 features
  • Scalability (28)
    9.9
    99%
  • Platform management overhead (27)
    9.7
    97%
  • Development environment replication (28)
    9.4
    94%
  • Platform access control (27)
    9.2
    92%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

No Charge

$0

Cloud
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $35 per month
Return to navigation

Product Demos

AWS Elastic Beanstalk Tutorial | AWS Certification | AWS Tutorial | Edureka

YouTube
Return to navigation

Features

Platform-as-a-Service

Platform as a Service is the set of tools and services designed to make coding and deploying applications much more efficient

9.5
Avg 8.2
Return to navigation

Product Details

What is AWS Elastic Beanstalk?

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).

AWS Elastic Beanstalk is designed for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS.

Developers can simply upload their code and Elastic Beanstalk automatically handles the deployment, from capacity provisioning, load balancing, and auto-scaling to application health monitoring. At the same time, users retain full control over the AWS resources powering their application and can access the underlying resources at any time.

There is no additional charge for Elastic Beanstalk - pay only for the AWS resources needed to store and run applications.

AWS Elastic Beanstalk Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

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).

AWS Elastic Beanstalk starts at $35.

Heroku Platform, Engine Yard, and Red Hat OpenShift are common alternatives for AWS Elastic Beanstalk.

Reviewers rate Ease of building user interfaces highest, with a score of 10.

The most common users of AWS Elastic Beanstalk are from Small Businesses (1-50 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(275)

Attribute Ratings

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Rahul Chaudhary | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Elastic Beanstalk has been around for some time, but it never caught our eye until we started using AWS CodePipeline.
Currently, we use Elastic Beanstalk (EBS) to run applications on our pipeline. Each stage (dev, perf, prod) has its own set of servers defined under EBS. Our current solution is working very well with CodePipeline.
  • Fits perfectly in our infrastructure. CodeCommit, CodePipeline, and AWS BeanStalk, work in perfect harmony.
  • Easy to change deployment configurations. If I need more servers in my EBS, I just change configurations, and with a click of a button I get more servers. For example, moving from nano instances to micro, or simply adding/deleting more servers.
  • Better security, and upgrade. I usually get small notifications of software/OS updates, and if I choose to, I can simply redeploy my application on an upgraded system.
  • Different upgrade strategies. I haven't tested all [of them], but the current one has the transactional type capability, where if my deployment fails, it falls back to the previous stable one.
  • Difficult to understand. No matter how cute and easy the AWS videos sound, I find it difficult to understand. There are just too many configurations.
  • EBS is free, but you pay for the resources. Problem is, I end up using more resources, thus paying more.
  • They could work on their logging system a bit more. I would love more dashboard metrics in logging, and an easier way to look at logs.
  • An option to make the default URL more friendly. I am forced now to use Route 53 to get a more friendly DNS name, but would have loved if they would have provided a better name to begin with. There are long random strings which could go away.
- It works perfectly with other AWS resources like CodeCommit, CodePipeline. If you are working in an AWS environment, this is a MUST.
- Once you understand how it works, you can use it to easily scale and manage your application.
- It certainly is better than its competitors.

- More AWS resources to manage. Great! Though AWS is easy, with so many options, it is getting tiring to learn more new AWS stuff. So be careful, EBS isn't hard, but isn't easy either.
- If you have a single server, you don't need it.
Platform-as-a-Service (11)
70%
7.0
Ease of building user interfaces
60%
6.0
Scalability
70%
7.0
Platform management overhead
70%
7.0
Workflow engine capability
70%
7.0
Platform access control
70%
7.0
Services-enabled integration
60%
6.0
Development environment creation
70%
7.0
Development environment replication
80%
8.0
Issue monitoring and notification
70%
7.0
Issue recovery
60%
6.0
Upgrades and platform fixes
90%
9.0
  • I spend less time managing infrastructure. So I plainly saved the cost of one employee.
  • I am completely invested to the AWS environment. Hence EBS is a natural choice. The ROI was significant because I am already invested in AWS.
  • Sticking to one vendor, means my team has to swim in familiar waters.
  • No extra access issues, because our IAM is already set up. Thus onboarding this technology wasn't difficult.
The biggest issue with using Beanstalk, and I guess with every other "infrastructure generators" are the same - what happens after it? You still have to manage it and understand what beanstalk did. So it was not as easy as it showed in the tutorial videos and diagrams. There is a learning curve, and eventually things do go wrong, so it is essential to understand what's happening under the hood.
AWS has good documentation, hands down. Initially I did feel that it was overwhelming, but the more time you spend with it, the easier it becomes. Beanstalk documentation is scattered, so definitely you need to look around a little bit. Other than that stackoverflow and medium like articles were my best friends.
Honestly, I haven't tried any other alternative products. As already mentioned, I am already heavily invested in AWS, so EBS was a natural choice for me. In other reviews, I have found, AWS is better than its competitors. There are more flavors, and options in AWS, better security, better models. Why go someplace else, when what you have serves you better.
1
In my small company, Beanstalk is used by the developers. However, in a larger organization, I can see it being used by DevOps team. Developers in my company use it for deployment and management of our applications and containers. It is used in conjunction with the pipeline tools that AWS provides.
1
Developers in my company use elastic beanstalk to deploy, manage, and monitor the applications in the servers. A developer must know and understand the basics of deploying an application and must understand the overall flow of the application development lifecycle. Having good understanding of AWS services is a given requirement. On top of that, having AWS certification is a big plus, and recommended.
  • Automatically provision the required servers to host the application.
  • Compatibility with AWS CodePipeline and CodeBuild.
  • Automatic scaling.
  • I wouldn't call it innovative, but having an end-to-end pipeline was a big achievement for us.
  • We were able to create our own EC2 images, compatible with beanstalk, with very small footprint which helped us reduce the cost by 20%.
  • We upgraded our beanstalk servers to work with containers.
  • We would like to trigger lambda functions from beanstalk servers.
  • We would like to associate ECS tasks with Beanstalk so that beanstalk can create servers on the fly to host more containers.
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.
No
  • Price
  • Product Features
  • Prior Experience with the Product
  • Existing Relationship with the Vendor
Beanstalk is part of AWS family, and if you are married to AWS like us, really you are left with little to no option to try other products. Obviously with technology it is possible to have other solutions, but it comes with more headache and price than just settling to use Beanstalk. And frankly it ain't that bad.
For us, we are pro-AWS. Other products in the market like Azure just doesn't cut it for us. Maybe in future we may want to use other vendors just for some simple applications, but not now. Documentation and community support is a big factor in choosing an infrastructure, and AWS excels in that. So if I had to choose again, I will choose the same stack.
  • Implemented in-house
No
Change management was a big part of the implementation and was well-handled
First and foremost, planning is the key to use any AWS service. When we initially started, we didn't know all the ins and outs of beanstalk. But we were smart in our implementation. Instead of just deciding that we want to use it, we did a couple of rough POCs to prove that our technology was supported. Then as we progressed, of course we hit issues and that led us to change the architecture multiple times, but each time we learned something new. So it is not a do and forget type of thing. It requires constant learning and be prepared for re-architecture.
  • Sometimes we didn't think our architecture all the way through, leading us to re-architecture and frustration.
  • Changing business requirement, led us to change the beanstalk usage. E.g. going from servers to containers.
  • We soon realized that AWS Is not cheap, and so we had to be clever to reduce our cost as much as possible.
- 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.
No
We are a small company, and we cannot afford for a premium support. Other than that, we actually are pretty good with AWS and technology. So far we haven't hit any issue that we cannot solve ourselves or with the help of the community. Additionally there are AWS blogs where we can get help for free.
No
So we never have directly interacted with AWS support, but we have definitely benefited from some of their staff member's answers and blog posts. In a recent example we were trying to reduce the volume size for our EC2 image. The solution was so specific that we could not find any question on stackoverflow that could help us. Upon searching AWS support site, fortunately we found the exact question that someone else had asked, and they got their answer pretty quickly. The answer was very detailed with step by step guide, so yeah it was an exceptional support for them, and it benefited us too!
  • Provision servers.
  • Integrate with out AWS services like AWS CodePipeline.
  • Scaling of servers.
  • Customization of EC2 scripts, e.g. you want to do something at the start when a new EC2 machine is booting up.
  • Managing IAM roles on top of the ones generated by Beanstalk.
Yes, but I don't use it
Score 9 out of 10
Vetted Review
Verified User
Incentivized
I used this as a backend hosting solution for my portfolio. I was looking to dive deeper into AWS solutions and this was a fairly easy way to do so with little upfront knowledge. I was looking at alternatives to hosting my site on another service's linux hosting solution and opted to give this try.
  • Scales well
  • Easy to spin up
  • CLI tools are great
  • Documentation was either lacking or too complicated for a beginner
  • The act of removing an instance took me several days to be sure it was actually removed and I wouldn't get billed for it
  • Billing information and estimates are hard to follow
The CLI made getting started incredibly easy. Tutorials made it fairly simple to get up and running without too much fuss. That said, it can be a very complicated solution if all you need is a basic hosting platform. However, it can scale out rapidly and does this amazingly well.
Platform-as-a-Service (10)
84%
8.4
Scalability
100%
10.0
Platform management overhead
90%
9.0
Workflow engine capability
80%
8.0
Platform access control
80%
8.0
Services-enabled integration
80%
8.0
Development environment creation
80%
8.0
Development environment replication
80%
8.0
Issue monitoring and notification
90%
9.0
Issue recovery
80%
8.0
Upgrades and platform fixes
80%
8.0
  • I was able to successfully host a SPA web app
  • It took me much longer to host a SPA using node than I originally thought
  • Overall it was a great learning experience and I would consider it again
AWS is much more focused on scalability, but Heroku was much easier to get things up and running as a beginner. For simple hosting, I would stick to something like Heroku or Netlify. That said, Elastic Beanstalk is meant for more performant functions requiring large scaling and I would definitely consider it for this type of task.
1
I was the only user of this service, primarily as a learning experience to see if it was a plausible affordable solution for hosting a simple portfolio site.
JavaScript full stack was required to make sure the app itself would run, but the general knowledge of Linux and CLI commands were necessary.
  • Quick deployment of web apps
  • Less worry about downtime of web apps
  • More insight into usage analytics of web app
  • Successfully got a SPA web app deployed in a relatively short amount of time. Expected more frustration than there was
  • May look into this as a solution for high traffic web apps
My particular use case did not justify the upkeep of Elastic Beanstalk
No
  • Price
  • Product Usability
  • Product Reputation
Price wasn’t lower than a previous hosting solution
I’d like a more established build pipeline to be able to support the ongoing builds and deployments to the instances
  • Implemented in-house
No
Just one initial phase to get a working solution in place for feasibility testing.
Change management was minimal
Sole developer, not applicable
  • Statically hosting and referencing assets on another AWS service from the build step took some playing with
  • Environmental variables were difficult to get working correctly
Spend some time investigating how to make the most use of Beanstalk before diving too deep. Take it in small chunks and learn as much as possible!
Great self help documentation covers most issues
No
I once got great help from the AWS team in regards to a lambda Alexa skill I was having issues with. Very quick resolution
  • The CLI makes it easy to get started
  • The configure file is pretty straightforward
  • Billing estimation seems hard to determine
  • Tutorials were a must to get started and feel somewhat confident
Great CLI and a growing group of people supplying tutorial information on how to make use of the system
Return to navigation