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).
AWS Elastic Beanstalk, the backbone of cloud applications & deployment
Elastic Beanstalk was perfect fit for our custom API
Fantastic Tool by AWS
AWS Elastic Beanstalk Gets Code into the Cloud with Minimal Difficulty
My amazing experience with AWS Elastic Beanstalk.
Climbing the Beanstalk: Best way to manage applications in the AWS giant's house
Good tool for deployments
The perfect PaaS tool if you are already using AWS
Serverless app autoscaling system for stateless applications!
AWS Elastic Beanstalk is the bee's knees!
Ideal for getting started
AWS Elastic Beanstalk, an easy way to move scale workloads
Amazon - never ceases to Amaze us!
Elastic Beanstalk Review
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
- Scalability (28)9.999%
- Platform management overhead (27)9.797%
- Development environment replication (28)9.595%
- Platform access control (27)9.393%
Reviewer Pros & Cons
Pricing
No Charge
$0
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
Product Demos
AWS Elastic Beanstalk Tutorial | AWS Certification | AWS Tutorial | Edureka
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
- 10Ease of building user interfaces(18) Ratings
Ability to build flexible user interfaces using drag-and-drop tools
- 9.9Scalability(28) Ratings
Ease of scaling up or down to meet demand
- 9.7Platform management overhead(27) Ratings
Resources required to keep platform up and running
- 9.5Workflow engine capability(22) Ratings
Process automation using rule-based engine
- 9.3Platform access control(27) Ratings
Rules controlling what data different user categories can access
- 9.8Services-enabled integration(27) Ratings
Ability to integrate with cloud applications and data via APIs and pre-built connectors
- 9.5Development environment creation(27) Ratings
Ease of creating new development environments
- 9.5Development environment replication(28) Ratings
Ease of replicating new development environments
- 9.1Issue monitoring and notification(27) Ratings
Integrated monitoring and notification of issues and problems
- 9.5Issue recovery(25) Ratings
Ease of recovery from problem state
- 9.4Upgrades and platform fixes(26) Ratings
Ease of deployment of major upgrades or problem fixes
Product Details
- About
- Competitors
- Tech Details
- FAQs
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 Competitors
AWS Elastic Beanstalk Technical Details
Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Unspecified |
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(274)Attribute Ratings
Reviews
(1-3 of 3)Amazon Elastic Beanstalk Review!
- Removes tedious, error-prone work from team focus for server configuration and environment setup.
- AWS creates new stacks when underlying software requires security updates, or frameworks release new versions.
- Greatly improves speed-to-production for many applications.
- Free resource on top of AWS; it costs nothing additional to use Elastic Beanstalk over the cost of the underlying instances and resources.
- 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.
- Scalability
- 90%9.0
- Platform management overhead
- 80%8.0
- Platform access control
- 90%9.0
- Services-enabled integration
- 90%9.0
- Development environment creation
- 70%7.0
- Development environment replication
- 70%7.0
- Issue monitoring and notification
- 80%8.0
- Issue recovery
- 80%8.0
- Upgrades and platform fixes
- 90%9.0
- Elastic Beanstalk removes countless hours from development team responsibility, freeing up those resources to instead focus on building the products that our customers want to use.
- As a business that is already embedded into using EC2 instances, it's essentially free to leverage the work that AWS performs on configuring the Elastic Beanstalk stacks.
- With Elastic Beanstalk, while there is still a responsibility to ensure that applications can work with updated underlying dependencies, it's much easier when AWS handled the heavy lifting of updating the stacks.
- Deploying and versioning code is very simple; Elastic Beanstalk maintains a configurable number of deployment instances, and you can rollback to any of them very easily
- Simple configuration options for type of deployment updates (rolling, all at once, immutable); shortens cycles in test while allowing for more complex strategies in production
- Simple auto-scaling support; easily use auto scaling groups to scale based on a number of custom triggers, easily attach policies for setting minimum and maximum numbers of instances
- Deploying to multiple regions unfortunately means deploying each one separately one-at-a-time
- Elastic beanstalk does not natively support sending process termination events to your application, so there is no way to gracefully terminate the application; rather, EB drains the instance at load balancer and then force kills the process
- Figuring out exactly what is running during updates, etc, can be difficult, and viewing consolidated logs to see what EB is running can be cumbersome
I am happy with my beans!
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.
- 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.
- 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.
- 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.
- Price
- Product Features
- Prior Experience with the Product
- Existing Relationship with the Vendor
- Implemented in-house
- 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.
- 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.
- 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.
AWS Elastic Beanstalk - Scales as advertised
- 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
- 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
- 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
- Price
- Product Usability
- Product Reputation
- Implemented in-house
- 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
- 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