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).
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Web Hosting Hub
Score 7.0 out of 10
N/A
Web Hosting Hub is a website hosting service with features such as SSD hosting, website backups, unlimited space and bandwith, and eCommerce tools.
N/A
Pricing
AWS Elastic Beanstalk
Web Hosting Hub
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
There are many services like AWS Elastic beanstalk, but there are none with the maturity in the platform or the cost-effectiveness of AWS Elastic Beanstalk. Also, AWS Elastic Beanstalk is the oldest among them, so there are more people with AWS experience than the other …
I have used App Engine on Google Cloud Platform and App Service on Microsoft Azure. Both offer similar capabilities to AWS Elastic Beanstalk. App Engine has the nice ability to scale to 0 instances when the application has not been in use for some time. This allows for …
As it supports end to end flow of application deployment and not a part of any individual process like other AWS products, AWS Elastic Beanstalk can be a game changer in cloud industry.
The AWS platform provides a great deal of configurability that is abstracted and provided very well through AWS Elastic Beanstalk. This is the main reason for choosing Elastic Beanstalk over competing services. Another reason for selecting AWS Beanstalk was vendor …
I selected AWS Elastic Beanstalk mainly because we have been using AWS services for our company. Using AWS Elastic Beanstalk is relatively easier than starting to use a completely new cloud platform. But we are also reviewing Google App Engine, and found out Elastic Beanstalk …
AWS Elastic Beanstalk is equivalent to Google App Engine in terms of product. I selected AWS Elastic Beanstalk because it was within the stack we were using, and it made sense for us given the other architecture.
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 …
Azure currently doesn't have a solution that's similar to this but you can do a lot of the features with several of the components that Microsoft Azure offers. AWS Elastic Beanstalk exists in that niche market where if you have an existing solution, this is a great way to move &…
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 …
AWS Elastic Beanstalk is a great option for an organization that's already invested in the AWS ecosystem. The greater the number of complementary features needed by the application (e.g. integrating with Amazon's Elastic Load Balancer, databases, etc), the greater the reward …
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 …
I enjoyed that Lightsail was so simple to provision and access via the in-browser SSH terminal, but ultimately Elastic Beanstalk is a more robust offering that interfaces seamlessly with more of AWS's other services. Elastic Beanstalk is also better equipped to automate …
I selected these solutions because they are the closest to being able to set up separate server or VM instances. As far as performance and scalability, Heroku does offer an autoscale option, but the base cost to have the autoscale in place, sets Heroku behind EBS. Digital …
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 …
Heroku is another similar product which we had tried out to deploy one of the NodeJs project and it has lot of developer friendly features as well. Though Heroku is more expensive than Beanstalk is what I found. Heroku also has some restrictions which can affect the …
The other main competitor that I have used would probably be Heroku. While Heroku is incredibly simple and easy to get a sample web app online, its dashboard and product connectivity didn't feel quite as seamless as AWS Elastic Beanstalk. AWS Elastic Beanstalk has a higher up …
In some of the other companies that I've worked in, I've had the opportunity to work with the above softwares where the structure and architecture of the services was much complicated but the above softwares were able to handle it with more ease and efficiency. The complex …
Web Hosting Hub is my preferred go-to when selecting hosting for a small business or freelance operation and it is also one of the lowest cost solutions that I have seen. This paired with their really excellent and always-available tech support (which I have called on …
AWS Elastic Beanstalk is well suited for [the] rapid development of applications that use standard compute platforms based on popular programming languages. So getting a Go, Python, Ruby, or Node.js app going in AWS Elastic Beanstalk will be easy. For non-standard applications, containers provide another option for using AWS Elastic Beanstalk. In either case, AWS Elastic Beanstalk is well suited for applications that are [self-contained]. AWS Elastic Beanstalk is also good for development or test environments that need a built-in deployment method. 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.
If you are a small business, freelancer, or any other type of user that doesn't need a lot of resources and get less than 10,000 hits per month, this is a great hosting environment for you. If you need more resources, I would recommend something else such as their sister company InMotion Hosting.
Easy setup - i can easily add domains, sub-domains, add-ons, as well as set up a WordPress installation in a matter of minutes.
Low cost - if you want to keep costs down, the plans are very cost effective with shared hosting for as little as $5 a month (there is a catch, that you have to sign up for a certain amount of time, but it's still worth it).
User-friendly UI via Cpanel - no surprises here, it's just a Cpanel that you're familiar with and works.
Excellent customer service and tech support available 24/7.
How to more easily integrate with other other AWS services. There are plenty out there, but it's not quite as seamless as I feel like it should be to mix and match products.
Make backing up easier when scaling the server. It took quite a bit of time to make sure we had everything set up in case something went wrong.
When you are first starting to use AWS, the dashboard can be very intimidating. There are countless products all with names that aren't very indicative of what they actually do.
Sites can be slow if you're on a shared server environment as they may be crowded servers.
Sometimes tech support doesn't know how to solve the problem - but I've only experienced this with one issue and that is site speed. likely the best solution is to upgrade to better hosting.
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.
The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares
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.
If there's a fix for the problem I'm having, they typically find it and help me implement it. In addition to that, they are available 24/7 to help so I know that they've got my back if I run into any problems whatsoever. Sometimes, wait times can be a little bit long, but honestly, the longest I've waiting was maybe 15 mins, so it's not too bad. Usually, I get through to them within 2-5 mins of calling.
- 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.
There are many services like AWS Elastic beanstalk, but there are none with the maturity in the platform or the cost-effectiveness of AWS Elastic Beanstalk. Also, AWS Elastic Beanstalk is the oldest among them, so there are more people with AWS experience than the other platforms. The only thing is their documentation and UX are a bit old, which doesn't stop it from performing greatly, but yes, if you are looking for better UX, then you can check out other options.
Web Hosting Hub is my preferred go-to when selecting hosting for a small business or freelance operation and it is also one of the lowest cost solutions that I have seen. This paired with their really excellent and always-available tech support (which I have called on holidays, weekends, and in the middle of the night) makes them a great option in my book.
In addition, they give you all the tools and access you need to manage your site no matter what you're trying to do. cPanel is a familiar environment and I have not noticed any bugs while logged in.
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.