[AWS Elastic Beanstalk] reduces the …
Platform management overhead (28)
Development environment replication (29)
Platform access control (28)
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of AWS Elastic Beanstalk, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Starting price (does not include set up fee)
- $35 per month
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.
- Abstract the operating system
- Availability and Uptime
- Ease of deployment
- I would like to see an easier way to backup
- Really very easy to build infrastructure and deploy the code.
- Amazing user interface which provides ease to build applications.
- Supports Multi platform like PHP, Python, Java, etc.
- Sometimes the deployment can be really very slow.
- Logs aren't very easy to analyze.
- Some of the EC2 metrics aren't showing after the recent update.
- 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.
- Users may find it confusing if they need to switch from the dedicated CLI for AWS Elastic Beanstalk and the AWS CLI.
- It would be useful to support paused or suspended environments for applications that don't need to be online 24x7. Dev and test environments would be benefit from this feature.
AWS Elastic Beanstalk is less appropriate for complex applications that rely on multiple AWS services. While deploying and running the base code might be easy to get going, it may be difficult to apply permissions and integrations with the other services.
[AWS Elastic Beanstalk] reduces the management complexity in a huge way with the customizable controls and options.
This also means a small overhead to start a project. AWS [Elastic] Beanstalk supports applications developed in Go, Java, .NET, Node.js, PHP, Python, and Ruby.
- Minimized overhead cost
- Expand the application support
- AWS Elastic Beanstalk was easy to implement, we only had to insert the application code to have it up and running in a few minutes. This helps us to launch company campaigns for different areas such as marketing, commercial and human resources.
- It has a fast learning curve, since the training material of the platform is public on the manufacturer's portal, furthermore it is easy to interact and intuitive for developers.
- The productivity of the equipment is optimized since they are not worrying about preparing the platform or infrastructure, they only have to attend to what is required by the application and its operation and this maintenance.
- The indicators and metrics that it has, ensure that the application cannot be saturated and have a performance problem, with AWS Elastic Beanstalk the application can scale resources when needed automatically.
- By having it as software as a service, we do not have all the government of the information to which the application codes are uploaded.
- It requires the intervention of an administrator for its management, even the routine maintenance of the platform is not very automated and requires the intervention of operating personnel.
- Its ecosystem and integration with third party software is not yet enriched, it is complex to manage if the AWS EB application is required to be integrated with another service in order to operate.
We usually took a long time to supply the infrastructure required by the application, even more so without knowing the fractional consumption that the application represented, since it was generally temporary or for campaigns lasting a few months.
- Comes with preconfiguration of all infrastructure service with EC2 instance.
- Developer with basic knowledge of cloud can also deploy applications.
- It comes with the optimum plan for various scenarios like high availability, consistency.
- It has almost all environments available for services.
- Not easy to do customization for some services.
- Not recommended for big environment back-end services.
- Customer support is okay!
- Providing managed application environments
- In-built load balancing
- In-built auto-scaling
- In-built logs and log aggregation through CloudWatch
- Providing managed updates to applications stacks
- In-built selection of deployment methods (all-at-once, blue-green etc)
- Integration with CodePipeline
- Some configuration options can be too rigid, and you have to delete an environment to change some configuration options.
- When things go wrong, they fail badly, and you are left with no insight or feedback.
- Some of the built-in monitoring metrics are hard to understand and configure.
- User has an option to choose servers they want to deploy such as Apache, IIS, etc.
- It is bit slow sometimes.
- It is fully automatic. You just upload your codes and EB will take care of the rest.
- It's well integrated with other AWS services like build pipeline.
- Good technical support from the documentation.
- Troubleshooting can be a pain. You cannot see where it was wrong exactly when you encounter errors.
- It can be touchy sometimes. You need to be very careful about what you have done and keep records on it.
- Mainly the two above.
- Deployment automation.
- Error handling.
- User interface.
- Easy to use.
- Extremely configurable.
- Deployment hooks could be a little more straight forward and easier to understand.
- Zero downtime deployments
- Auto scales, ensuring maximum flexibility.
- Auto scaling also provides a cost saving as you only use what you need.
- Agile deployments - dev environments regularly have 5+ releases a day.
- More flexibility on the subnet structure (depending on use case scenario and how your VPC is carved up you can run out of address space quickly if you want to spread workloads across multiple AZs).
- If development teams need Elastic Beanstalk admin access.....they automatically get EC2:* permisisons which isn't ideal.
- A lot of the drawbacks can be addressed by using ECS.
- Affordable way to scale computing with little involvement
- Easy set up and ramp up
- Good toolbox for several platforms with flexibility
- Spinning up additional nodes can sometimes be slow based on your implementation
- Testing the scaling can be tricky
- Implementation of your code still needs to be solid or else you'll have some issues
- Supports multiple popular languages to be deployed easily and helps in saving developers' time.
- Helps in scaling and load balancing based on the number of requests it is handling.
- Provides a neat monitoring system for the servers running along with the access to the logs which can also be downloaded if required.
- Can include more languages to be deployed (say Erlang) and not only popular languages.
- Issues in packaging large applications, say more than 2GB to be frequently deployed by uploading the packages to quickly test something.
- Takes considerable amount of time to just deploy simple applications on Elastic Beanstalk, can be frustrating for developers.
- Fast to deploy
- Easy to get up and running
- Easy to manage
- Command line interface could be easier, but it still works.
- Documentation could be better
- Deployment management is very good.
- Configuration and monitoring are easy.
- There's no need for complicated configuration issues. You can deploy your application in minutes.
- It should accept deployment from S3 buckets.
- You cannot store old deployment packages up to 500.
- 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.
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.
- Easy to set up deployment of many technologies.
- Handles everything from app to database.
- Integrates into IDEs for easy deployment.
- For .NET - it doesn't quite compete with some of the Azure stuff when it comes to ease of use.
- When there are problems, they can be hard to track down what went wrong.
- It's AWS - so it always has that AWS learning curve for getting set up initially and configuring things.
- 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
- Extremely easy to get set up and get apps deployed.
- Integrates really well with existing build processes and is manageable through a suite of CLI tools.
- It is very easy to scale up.
- The documentation is exceptionally detailed and covers a very wide range of deployment scenarios.
- The product is generally very good, but if there is one thing I'd improve it is the web-based user interface for managing instances.
- I wish the storage configuration was a little more intuitive. It would be nice to get up and running without having to learn about S3 first.
- Interface isn't as streamlined or intuitive as it probably could be.
- Readily available environments
- server crashed and reset, losing our files, within the first week, and again later
- support was a minimum of $27 and they did not give a response as to why the server reset
- the most unreliable hosting i've ever used in more than 10 years of web development
- all amazon's services are over-thought in nature
Bottom line, if you want support that gets back with you in less than 24 hours, do not use these people.
- Elastic Beanstalk is a great product that provides tools for running your web application in few simple steps.
- It works on top of the AWS EC2 and provides autoscaling, logging, monitoring for you out of the box.
- Its security features are great, for those who are looking for it.
- Their help and support is exceptional.
- It has so many options and packages, that it is overwhelming for a newcomer.
- I don't like the dynamic attribution of security groups: the names are random, so it's hard to understand what is going on.
- The only disadvantage of using EBS is that the instance that gets setup as a part of the EBS environment isn't customizable since the users do not have access to that instance.
- Cost effective
- Scalable and reliable
- LOADS of features
- AWS as a whole can be intimidating, or hard to learn
- Additional complexities are added at times due to nature of AWS/Cloud