AWS Elastic Beanstalk Reviews

I was using AWS Elastic Beanstalk to deploy my application and to learn data engineering concepts. I used AWS Elastic Beanstalk to test how to change data from raw to useful cases. In that way, I used it for deploying my application. I haven't used AWS Elastic Beanstalk directly for my company, but I have used it for my own learning.

AWS Elastic Beanstalk made the deployment quick and hassle-free. The platform handled most of the heavy lifting automatically, which saved me a lot of time. The scaling feature is very helpful, as the automatic scaling worked really well. I only need to adjust the capacity without having to do anything manually. The scaling features were one of the best parts, as it handled the load changes effortlessly. The environment configuration provided a very good user experience. Setting up the environment was straightforward, and the UI and presets made the configuration very simple. Everything was neatly organized in the console.

The performance and reliability of AWS Elastic Beanstalk were solid. My application ran constantly without any major issues, and the reliability was very good. AWS Elastic Beanstalk kept everything running smoothly even during high traffic, so I would definitely recommend it to others.

I love the automation of AWS Elastic Beanstalk as it managed the deployment, scaling, and health monitoring for me. The simplicity is definitely what I like the most, as it can be used for production-ready applications without dealing with complex infrastructure. The logs and monitoring tools are very useful; the health dashboard and the logs gave me clear insights into what was happening. The monitoring tools were useful and very easy to access, making troubleshooting very quick. The documentation was also very clear and easy to follow, and I found almost everything I needed. The support was good, and the docs were detailed enough to help me through the setup and deployment.

The overall experience with AWS Elastic Beanstalk was excellent. The performance made deploying and managing my application very easy, and it was really smooth and efficient. The automatic scaling can be improved so it can handle traffic changes more smoothly.

I have given a rating of nine out of ten because auto scaling works reliably and it handles traffic spikes well with minimal manual effort needed. There is a balance between simplicity and control. I have not given a ten out of ten because sometimes the scaling decision can feel slightly delayed depending on the metrics. AWS Elastic Beanstalk is powerful, but not as advantageous or granular as ECS or EKS auto-scaling. Customization is good but not fully flexible for complex architectures.

I have been using AWS Elastic Beanstalk for one year.

AWS Elastic Beanstalk is very stable according to my experience.

AWS Elastic Beanstalk works reliably and handles traffic spikes very well with almost no manual efforts. It is very powerful but not as advanced or granular as ECS or EKS auto-scaling.

The customer support for AWS Elastic Beanstalk is good. Although I haven't taken any help from customer support, I think it is good because all the phone numbers and email addresses are clearly mentioned if you need any help.

When I was using AWS Elastic Beanstalk, it was my first cloud experience. I was learning some concepts from YouTube, and that person was using AWS, so I have used AWS only.

I have seen a return on investment in terms of time saved as well as simplicity.

My experience with AWS Elastic Beanstalk regarding pricing, setup cost, and licensing was good compared to other services.

There is nothing that makes me frustrated while using AWS Elastic Beanstalk. I would definitely recommend AWS Elastic Beanstalk to others as it is perfect for quick deployment with minimal infrastructure overhead. It is a great choice for developers who want to focus on their code instead of server management. My overall review rating for AWS Elastic Beanstalk is nine out of ten.

I use AWS Elastic Beanstalk for end-to-end application deployment for web applications of various types. I have deployed Python, .NET, and Java applications through it.

The management of environments is a valuable feature. It integrates well with other AWS services, especially with RDS and S3. AWS Elastic Beanstalk helps me manage and control deployments, which are straightforward, speeding up the process of getting applications up and running.

One area where AWS Elastic Beanstalk struggles is with the complexity of deployments. As deployments become more complex, technical constraints can become a burden. This can lead to a situation where I might be better off building my own deployment mechanism. 

Additionally, CloudFormation controlling AWS Elastic Beanstalk in more complex environments is poorly supported, which can make management challenging.

I have been using AWS Elastic Beanstalk since it was released in 2013.

AWS Elastic Beanstalk is great for scalability since it is built on AWS infrastructure, allowing it to scale well for standard deployment-based applications. However, when dealing with complex deployment scenarios, it can be difficult to manage, and at some point, developing a custom deployment mechanism may be necessary.

The service itself is free to use, and I am charged for the infrastructure that is utilized as a result of the application running. Thus, recurring spending arises from the infrastructure setup process, while the management service is free.

For newcomers, it is best to dive in and use AWS Elastic Beanstalk. It is ideal for applications that existed before and need to be deployed quickly in a controlled manner. It works extremely well for such cases. I highly recommend it to others and frequently discuss it with customers. I would rate the overall solution a nine out of ten.

I use the solution to deploy a web application written in Python. It is a service that allows me to deploy my application to a live environment with admin provisioning for other necessities like security and infrastructure. I did not have to do anything beyond deploying my application on the account, which then went live.

The feature I like most about Elastic Beanstalk is the way I do not have to do anything, just deploy my app.

Elastic Beanstalk is powerful, however, it could be enhanced in areas where it abstracts infrastructure management, sometimes limiting advanced users who want granular control over resources like EC2 instances, networking, or load balancers. 

Logs and debugging can sometimes be cumbersome, and there could be a more seamless method to analyze application issues without relying heavily on CloudWatch, which would improve my experience. 

The deployment speed could also be improved, as it can be slow, especially for large applications. Optimizing the deployment pipeline could save time. Integration with CI/CD tools could be seamless with external CI/CD tools like Jenkins or GitHub Actions to simplify the setup process.

I have used it for probably two months.

There was a time I tried to deploy an application, however, there was an error I struggled to pinpoint. I checked the logs but could not identify the issue until I returned to AWS EC2 instances or ECR. 

Eventually, with GitHub Actions, I realized there was an error on one of the pages of the application written in Node.js. Once I identified it, I deployed it back to Beanstalk, and it went through.

It is easy to scale. AWS makes it easy to scale up with auto-scaling and Elastic Load Balancing. AWS automatically adjusts the load balancing after distributing incoming traffic and the auto-scaling group, which dynamically adjusts the number of EC2 instances in the environment.

Amazon Beanstalk is designed by AWS to be set up with minimal configuration required. I deployed an application by simply uploading the code, either as a ZIP or WAFA file, and the desktop took care of provisioning resources like EC2. It is easy, and I can directly control versioning with Git for easy deployment through the command line.

The last time I used it, it was free since it was for development. The pricing is okay. 

Elastic Beanstalk, based on my experience and recommendations from friends, is a good solution.  

I would recommend AWS since it is easier to use, and I do not have to do many things before hosting my applications in a live environment. 

I rate the overall solution as nine out of ten.

Elastic Beanstalk is used in deploying and scaling web applications and services. It helps us deploy and scale web applications on Amazon Web Services cloud. This solution is suitable for managing capacity provisioning, load balancing, auto-scaling, and application health monitoring.

Elastic Beanstalk simplifies deploying and managing applications. It allows our applications to be scaled to serve millions of users, ensuring low latency. It supports multiple programming languages, facilitating diverse application deployments.

Elastic Beanstalk simplifies the process of deploying and managing applications. It allows our applications to be scaled to serve millions of users, ensuring low latency. A notable benefit includes multiple programming language support, including PHP, Java, Python, Node.js, Ruby, .NET Core, and Docker. This enhances the ability of our developers to utilize different frameworks.

Elastic Beanstalk can enhance its customizability further, especially in terms of deployment options.

I have been working with Elastic Beanstalk for the past five years.

Elastic Beanstalk is very stable, as it automates many tasks and scales automatically to manage load. I would rate its stability as eight out of ten.

Auto-scaling is very important for Elastic Beanstalk, as it helps scale applications based on their needs without manual intervention. It manages load by scaling up when needed and down when there is less demand. I would rate the scalability as a ten out of ten.

I am not directly involved with technical support, however, based on my perspective, I would rate the customer support as eight out of ten.

Positive

While I don't handle the technical setup, based on the information and resources available, I would rate the initial setup as six out of ten.

Elastic Beanstalk does not have additional charges and integrates well with existing AWS resources. Pricing is inclusive of the technologies and instances used, making it efficient.

Elastic Beanstalk helps reduce system administration as it automates many tasks. Developers can focus more on application development and less on managing deployments.

I would rate the overall solution as ten out of ten.

I use Elastic Beanstalk as a fast service to simplify my work. I use it by uploading code in Java, Python, or any other language to create a platform. Elastic Beanstalk manages configurations such as server requirements and allows Bluegreen deployments and other tasks through its environment.

I like the services, such as the common service I use here. Elastic Beanstalk is helpful and easy to manage services, even when dealing with multiple clients. It is a straightforward service, and I can leverage CloudFormation to create stacks and automate processes. AWS support is very helpful and allows me to manage tasks and projects effectively.

There are areas for improvement in Elastic Beanstalk, especially in the management part. Tasks like creating load balancers and retiring versions require manual code updates, and URL changes can be time-consuming. Some challenges arise from having to update URLs and swap with domain providers during Bluegreen deployments.

I have been using it for the last three years.

Elastic Beanstalk's stability is generally good. I faced issues with EKS during upgrades, but fortunately, it did not affect production. Elastic Beanstalk is a straightforward service with some minor challenges with retired versions and load balancer creations.

I manage scalability easily using my scaling group and CloudFormation. For EKS, I handle scaling by defining thresholds for minimum, desired, and maximum requirements.

Amazon’s support team is really helpful, as I use AWS as an enterprise service. However, sometimes differing opinions from the support team can be challenging. I use their documentation to verify advice. Overall, they are very helpful.

Neutral

I would rate the product overall as a seven out of ten.

If someone has knowledge of AWS, the solution is easy to use. AWS provides good support, however, having additional knowledge helps.

We primarily use Elastic Beanstalk to deploy web applications, mostly built with Django, Laravel, or even native PHP. It provides two options: deploying directly on EC2 or using a Dockerized environment on EC2. This distinction is crucial because Elastic Beanstalk manages your entire platform's environmental configuration. For example, with Django, it handles your Python virtual environment. Similarly, for PHP, it takes care of PHP-FPM configurations, NGINX configurations, and more.

Another incredibly useful feature is the ability to add configuration files directly to your repository. These files allow you to make modifications to the environment. For instance, you can alter server settings like maximum memory or adjust NGINX configurations. These changes are automatically applied through pre-deployment and post-deployment hooks.

Furthermore, we install certificates directly within Elastic Beanstalk using our repository. This eliminates the need to SSH into the server. It's all streamlined and readily available out of the box.

One of the most valuable aspects is that developers can access logs directly. They can download them from the AWS console within Elastic Beanstalk, eliminating the need to request logs from me. This allows them to quickly retrieve, for instance, the last hundred lines of logs.

Another key benefit is the seamless management of rollbacks. If any issues arise during deployment, your website keeps on running. This is because deployments occur in a separate folder. Once deployment is complete, a simple folder rename ensures a swift website update, typically taking only a second or two.

Furthermore, session management between Elastic Beanstalk and RDS is handled very well and efficiently. You don't have to worry about sessions as they are preserved while code updates are seamlessly applied in the background.

From what I've observed, it seems AWS has ceased further development on Elastic Beanstalk. Perhaps they're shifting their focus away from it. They've discontinued many features and are even recommending alternatives like EKS and other serverless services. I've also come across numerous questions online from people encountering issues with Elastic Beanstalk. 

It seems to be a common concern that AWS is no longer prioritizing Elastic Beanstalk. Instead, they appear to be concentrating on serverless offerings. While this may be disappointing for Elastic Beanstalk users, I believe it's a positive move. Serverless represents the future.

AWS could consider adding more platforms as managed services within Elastic Beanstalk. Currently, they offer around five or six. However, since it already provides a Dockerized environment, you can essentially run any language you prefer. So, in my view, they pretty much have everything covered at the moment.

I've been working with AWS Elastic Beanstalk for four years now, and it's still working great. I’m currently using it for new projects as well.

I find it to be stable. While every service has its pros and cons, Beanstalk is genuinely stable if you monitor it properly. To be honest, it rarely goes down. If you configure AWS services correctly with alarms, Elastic Load Balancing, and other best practices, downtime should

It's definitely scalable. You simply need to specify the desired number of instances. However, it doesn't offer automatic scaling. You have to define the range of servers you want running at all times. For example, you could set a minimum of two instances and a maximum of five or ten. Within that range, it scales automatically.

For Elastic Beanstalk, we're running around ten to twelve environments. I manage the DevOps side for most of them, but developers also utilize it to access logs and monitor deployments. This simplifies their workflow significantly, as they can easily verify if everything is deployed correctly in their dev and stage environments. They don't typically access production, though.

We reached out to AWS support in early 2021. We were having trouble deploying .ebextensions files. We wanted to run certain commands, like Cron jobs, within Elastic Beanstalk using the repository. They were very helpful and assisted us in resolving the issue.

Positive

I've used AWS and also explored other vendors, like competitors. I've tried Google App Engine. I was searching online for alternatives to Elastic Beanstalk, and App Engine came up as a potential replacement as a Platform as a Service offering.

They provide a similar YAML file for configuration and deployment, but I found it quite confusing. We encountered a lot of errors, and it wasn't very straightforward to deploy. There were many things to consider initially, including the versions of your application and App Engine itself. App Engine offers limited versions of PHP, Python, and other languages, which can be restrictive.

This version limitation was a major issue we faced with App Engine. Ultimately, we decided not to proceed with it and stayed with Elastic Beanstalk.

Initially, we deployed using both the console and the CLI. The CLI is faster and provides more control than the console, but we generally prefer the console. We use a multi-tier architecture with two EC2 instances and one load balancer.

Importantly, we do not include the database directly within the Elastic Beanstalk installation. This is because if you add RDS to Elastic Beanstalk, deleting the environment also deletes the database. There's no way to avoid this, which is a significant drawback.

Next, we have AWS CodePipeline configured to pull code from GitHub or Bitbucket. We then deploy it directly, potentially including stages like CodeBuild for testing or SonarQube for analysis, if needed.

Deployment itself is straightforward. You simply select your Elastic Beanstalk environment and the application you want to deploy, such as dev, prod, or stage.

Crucially, you need two folders in your repository: .ebextensions and .platform. .ebextensions provides additional control. For instance, you can place commands.config within it to execute platform-specific commands. These could include running database migrations after deployment or other post-deployment actions.

We primarily utilize .platform for NGINX configuration, PHP configuration, or any other platform-level adjustments.

Finally, we just push the code to GitHub, triggering an automatic deployment. Any errors that occur are visible in the console or CloudWatch.

I recommended this to a friend, and it took him about a week. However, he encountered numerous issues and had to consult me multiple times because he couldn't find the right answers online. So, for him, it took about a week to complete the deployment.

The deployment process would ideally require two people if you want to do it really quickly. You should also have a solid understanding of the server side, especially with Linux.

It does require maintenance. Sometimes the code doesn't deploy on the server for some reason. The servers get stuck, and the deployment fails. You have to manually restart the EC2 instance. You can't always rely on the code deploying automatically. It happens to us about once every four months, but it does happen from time to time.

The time-saving is immense. We don't have to manage the Linux server, patch it, update packages, or worry about restarts and weekly maintenance. It handles all of that automatically. Deployment is incredibly fast, as developers simply push to branches, which then trigger automatic deployments to Elastic Beanstalk.

Overall, the deployment process is streamlined, maintenance is minimal, and it saves us a tremendous amount of time.

Elastic Beanstalk itself is free of cost. You only incur costs for the EC2 instances or load balancers you're running with it. The platform itself is completely free.

Overall, I would rate it a nine out of ten. I would recommend it to other people. If they're trying to deploy a web application on any cloud provider, I'd strongly suggest going directly with Elastic Beanstalk instead of managing an EC2 instance themselves. It's much simpler to use Elastic Beanstalk and deploy your code out of the box. It just works.

I work with EC2, S3 for storage, Elastic Beanstalk, CloudFront, and CloudWatch.

AWS Elastic Beanstalk helps improve my efficiency, saves time, and streamlines application hosting in the cloud.

Elastic Beanstalk is valuable because it auto-scales servers, which enhances application performance by expanding resources automatically when needed.

Sometimes there are issues when auto-scaling with CloudFront. In terms of integration with CloudFront and monitoring, it needs some improvement.

I have been working with Elastic Beanstalk for around six months.

I have not experienced any stability issues. It is fine.

Elastic Beanstalk auto-scales according to the application needs, which makes it very scalable.

I haven’t escalated any questions to AWS tech support.

Before cloud solutions, one needed to manually handle all the servers, purchasing extra servers to increase capacity.

The initial setup is straightforward. It involves setting up several components like EC2 servers and storage as part of a sequence of steps.

Using AWS Elastic Beanstalk has improved operational efficiency and saved time, indicating a positive return on investment.

The pricing of AWS Elastic Beanstalk is based on usage duration and space. It is reasonable, with minimal costs, especially for short-term use.

I would recommend AWS Elastic Beanstalk due to its ease of use, time-saving features, and cost-effectiveness.

I'd rate the solution nine out of ten.

My primary use case for AWS Elastic Beanstalk is to train instructors in Pakistan, mainly focusing on services like S3, Amazon EC2, Elastic, Beanstalk, and LoadBalancer. I also use it when working with clients who are migrating to our services, as it provides an easy and manageable way to understand services.

AWS Elastic Beanstalk has helped manage projects easily without the need for installing patches or worrying about configurations. It allows me to delegate tasks to students or interns securely, with Amazon handling failures or any issues.

The most valuable feature of Elastic Beanstalk is its ease of use and management. I don't need to worry about installations or maintenance as it is an Amazon-managed solution, which allows me to focus on other tasks.

AWS Elastic Beanstalk could improve its auto-scaling feature to better detect potential AI-based attacks or misuses that could lead to unexpected costs.

I have been using Elastic Beanstalk for about two to three years.

I have never experienced any stability issues with Elastic Beanstalk. It does not have bugs or break down unexpectedly.

The auto-scaling feature is a good concept. It needs refinement to assess real attacks versus artificial spikes effectively.

The free support from Amazon has been helpful for us in dealing with billing issues, although we rarely need technical support.

Neutral

I handle the implementation with my team of students and interns.

AWS charges for support services, and the costs for AWS Elastic Beanstalk can be high compared to on-premises or other cloud solutions like VMware.

Some of the solutions evaluated included Alibaba and VMware, mainly due to their lower costs.

I would rate Elastic Beanstalk a seven out of ten due to its ease of use, but the high cost remains a concern. I would recommend it to others because of its convenience, especially for students learning about cloud services.

I'd rate the solution seven out of ten.

I use AWS Elastic Beanstalk for deploying my web application on the cloud. I do so within the context of my project for my master's program.

Elastic Beanstalk is very easy to use, providing infrastructure to deploy our third-party application to the cloud within 15 to 20 minutes. It is very helpful for our web application developers and usage companies. It is cost-effective, easy to use, and provides useful security for our applications on the cloud.

Sometimes it is difficult to use for the first time. The automatic scaling functionality could use improvement.

I have been using AWS Elastic Beanstalk for around six months.

I have not faced any issues with stability since everything worked on my first try.

It is easy to use after getting the hang of it initially, which might be slightly challenging. You can utilize a batch file to deploy your application directly.

It is cost-effective, providing security and ease of use.

Beanstalk is rated a nine out of ten.