We performed a comparison between Amazon EC2 Auto Scaling and AWS Lambda based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Both products are very effective in providing compute service (IaaS) solutions. AWS Lambda slightly nudges ahead of Amazon EC2 Auto Scaling as many users feel it is easier to code using the solution. AWS Lambda is serverless, server configuration is not required, and can easily run it directly anywhere.
"The auto-scaling feature is particularly useful. Additionally, CloudWatch and CloudTrail are also important features for us."
"The most valuable features are that it is stable, flexible, and reliable."
"Most of what I've deployed are CI/CD pipelines. AWS is scalable. You can always increase or adjust the resources to meet the specific requirements. I also like choosing an instance in any location, preferably the closest one. We don't have any AWS locations in South Africa, but the latency is about the same as hosting in Europe."
"The most valuable feature of Amazon EC2 Auto Scaling is scaling your intra based on the request. Additionally, you are able to map the solution with any load balancer, such as public or private load balancers."
"Amazon EC2 Auto Scaling has good integration."
"The tool helps me to process large data sets while scaling up."
"The most useful feature is elasticity. You can scale up or down based on traffic."
"What we have found most valuable are the purchasing of usage at the time and small storage."
"The most valuable feature of this solution is the API Gateway."
"AWS Lambda is itself serverless, and it is connected to the API gateway, and you can directly call the API through the API gateway and connect through AWS Lambda."
"I like the pay-for-what-you-use feature. This is the main reason why we use AWS Lambda. I don't have to manage servers; I just have to configure Lambda and expose it to an API gateway."
"Thanks to this solution, we do not need to worry about hardware or resource utilization. It saves us time."
"Lambda being serverless is a great feature that is appropriate for our use cases."
"The solution is designed very well. You don't need to keep a server up. You just need some router to route your API request and Lambda provides a very well-designed feature to process the request."
"I think the most valuable feature is the agility of the solution."
"I like that it's easy to use and maintain. Lambda is good and supports different platforms, so you don't need to worry about language or maintenance."
"I would like to see a feature included that has the capability to clone when an instance is being terminated."
"Automation is very hard."
"The launch configuration feature doesn't work properly. It needs to improve the load configuration feature along with launch templates. The tool needs to tag feature as well."
"Its stability and scalability need improvement."
"I would like to see the security portal improved in the future."
"As we are transitioning to managing containerized applications, the solution could improve by adding more managed container services as a feature in the solution."
"The price could always be a bit better."
"The product does not explain why a particular instance is terminated."
"AWS Lambda needs to improve its stability."
"Lamba functions have cold-starts that can cause some delay."
"If you're running a new application with a significant load, you need to be prepared for potential bottlenecks."
"The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one"
"The overall performance of this solution could be improved. We would also like to have better integration with other AWS features."
"It could be cheaper."
"The feature to attach external storage, such as an S3 or elastic storage, must be added to AWS Lambda. This is its area for improvement."
"The execution time could be better. One of the major limitations is the time period because it doesn't give you more than seven minutes. So, before thinking about Lambda, you should think through your use case and ensure it's a good fit. Otherwise, you can use batch, step functions, or other methods. Reports and the monitoring board could also be improved in terms of alerts. The threshold alerts are there but can be improved. It takes some time to get used to these methods and get the hang of them."
Amazon EC2 Auto Scaling is ranked 2nd in Compute Service with 36 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. Amazon EC2 Auto Scaling is rated 8.8, while AWS Lambda is rated 8.6. The top reviewer of Amazon EC2 Auto Scaling writes "Well-documented setup process and highly stable solution". On the other hand, the top reviewer of AWS Lambda writes "An easily scalable solution with a variety of use cases and valuable event-based triggers". Amazon EC2 Auto Scaling is most compared with AWS Fargate, AWS Batch, Amazon Elastic Inference, Oracle Compute Cloud Service and Apache NiFi, whereas AWS Lambda is most compared with AWS Batch, Apache NiFi, Apache Spark, AWS Fargate and Google Cloud Dataflow. See our AWS Lambda vs. Amazon EC2 Auto Scaling report.
See our list of best Compute Service vendors.
We monitor all Compute Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.