# AWS Lambda Reviews **Vendor:** Amazon Web Services (AWS) **Category:** [Cloud Platform as a Service (PaaS) Software](https://www.g2.com/categories/cloud-platform-as-a-service-paas) **Average Rating:** 4.6/5.0 **Total Reviews:** 990 ## About AWS Lambda AWS Lambda lets you run code without provisioning or managing servers. You pay only for the compute time you consume - there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service - all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app. ## AWS Lambda Pros & Cons **What users like:** - Users appreciate the **ease of use** of AWS Lambda, enabling quick implementation and management of serverless applications. (47 reviews) - Users appreciate the **scalability** of AWS Lambda, benefiting from automatic scaling that adapts to varying workloads effortlessly. (35 reviews) - Users value the **cost-effectiveness** of AWS Lambda, enjoying savings and efficiency for dynamic, high-load tasks. (27 reviews) - Users find AWS Lambda's **serverless compute capabilities** essential for scalable applications and automated tasks like report generation. (23 reviews) - Users value the **seamless integrations** of AWS Lambda with other AWS services, enhancing development efficiency and scalability. (22 reviews) - Easy Setup (19 reviews) - Automation (13 reviews) - Deployment Ease (10 reviews) - Reliability (10 reviews) - Implementation Ease (9 reviews) **What users dislike:** - Users find the **resource limitations** of AWS Lambda restrict its use for larger datasets and heavy workloads. (36 reviews) - Users find **difficult debugging** in AWS Lambda challenging due to abstracted environments and reliance on logs for issue tracing. (17 reviews) - Users note that **slow performance** , especially during cold starts, can significantly hinder the effectiveness of AWS Lambda. (13 reviews) - Users experience **lagging performance** with AWS Lambda due to slow startup times and execution limits on functions. (10 reviews) - Users find AWS Lambda **expensive** , especially when factoring in additional tools and unexpected charges from usage patterns. (9 reviews) - Limitations (7 reviews) - Users note that **complexity in configuration and dependency on external services** can hinder effective use of AWS Lambda. (5 reviews) - Missing Features (3 reviews) - Scaling Issues (3 reviews) - Cost Transparency (2 reviews) ## AWS Lambda Reviews ### 1. Serverless, Cost-Effective Performance Testing with AWS Lambda **Rating:** 5.0/5.0 stars **Reviewed by:** Chetan M. | Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** April 02, 2026 **What do you like best about AWS Lambda?** It’s serverless, so we don’t have to worry about managing servers—AWS handles that for us. We use AWS Lamda for running our performance tests, we don't have to keep server running, whenever we need we can spin up and run the tests for API's, good for short running tasks. Easy to maintain and integrate it from command line. Price wise also we don't spend much since it's costing us for what we run. Later to trouble shoot issues, we cna go to UI and check the aws cloudwatch logs, AI can help as well if we want are trougble shooting something specific, and onboarding same process for other env is easy. **What do you dislike about AWS Lambda?** I wish it could support more than 15 minutes; if they could extend it to 30 minutes, that would be great. Also, it takes a while to bootstrap and start running. **What problems is AWS Lambda solving and how is that benefiting you?** We use AWS Lambda to run our performance tests, which is very important because our app has been live for 5 years and customers use it every day. Every quarter, we run performance tests to make sure our APIs meet our SLA metrics. AWS Lambda is very helpful for getting these stats and covering this scenario for us. ### 2. AWS Lambda simplifies automation and the execution of serverless logic **Rating:** 4.5/5.0 stars **Reviewed by:** Caleb F. | Data & IA Specialist, Small-Business (50 or fewer emp.) **Reviewed Date:** March 10, 2026 **What do you like best about AWS Lambda?** What I like most about AWS Lambda is that it allows you to execute business logic and automations without having to manage servers. It is very useful for building lightweight integrations, responding to events, and decoupling processes within an AWS architecture. I also appreciate that it integrates well with other services like S3, EventBridge, Step Functions, IAM, and CloudWatch, which greatly facilitates the construction of serverless workflows. For specific tasks, event processing, and auxiliary components of pipelines, it is very practical and scalable. **What do you dislike about AWS Lambda?** What I like least is that debugging and troubleshooting can become more complex when the function depends on multiple services, permissions, or external configurations. There are also limitations that require careful design of certain use cases, such as maximum execution times, handling heavier packages, or specific dependencies. In some scenarios, monitoring errors or understanding integration failures takes longer than expected. **What problems is AWS Lambda solving and how is that benefiting you?** AWS Lambda helps address the need to run processes on demand or event-based without provisioning or maintaining infrastructure. In my case, it is useful for automations, middleware logic between services, and auxiliary tasks within data flows and operational processes in AWS. The main benefit is that it reduces operational load, accelerates the development of integrations, and allows for building scalable components in a simpler and more flexible way. ### 3. True Zero-Administration Serverless Model That Lets Us Focus on Coding **Rating:** 4.0/5.0 stars **Reviewed by:** Muhammad Awais A. | Sr ICT Engineer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** January 24, 2026 **What do you like best about AWS Lambda?** It’s truly a zero-administration, serverless model, so there’s no need to manage hardware or worry about patching the operating system. It allows me and my team to focus 100% on writing code instead of spending time on server maintenance and ongoing upkeep. **What do you dislike about AWS Lambda?** Debugging and observability: When you’re debugging but don’t have access to the underlying server, you can’t SSH in to see what’s wrong, which makes troubleshooting much harder. **What problems is AWS Lambda solving and how is that benefiting you?** Traditionally, a small script to monitor a network or check a license required a dedicated server or VM, which then needed OS patching, security hardening, and ongoing monitoring. With Lambda, I can deploy code to handle a specific task without managing the underlying infrastructure. This removes the overhead of maintaining utility servers, and lets me run automation scripts for infrastructure without the burden of patching and maintaining a Linux box just to host a single Python script. ### 4. Zero Server Management and Seamless Auto-Scaling with AWS Lambda **Rating:** 4.5/5.0 stars **Reviewed by:** Chandan D. | Staff Software Development Engineer Test, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about AWS Lambda?** The best part of AWS Lambda is that there’s essentially zero server management. Not having to patch OS versions or manage clusters lets our engineering team focus fully on writing and improving code instead of dealing with infrastructure overhead. The event-driven model also feels seamless—triggering functions from S3 uploads, DynamoDB changes, or API Gateway requests simply works as expected. On top of that, the scaling is impressive: whether we see 10 requests or 10,000, Lambda handles the concurrency without us needing to tweak a single scaling policy. **What do you dislike about AWS Lambda?** The “Cold Start” issue is still a factor, particularly for functions written in Java or .NET, and it can add slight latency when requests are infrequent. In addition, the 15-minute execution limit means it isn’t a great fit for long-running or heavy data-processing tasks. With these constraints in mind, you really have to be intentional about how you design and architect your workflows so everything stays within the guardrails. **What problems is AWS Lambda solving and how is that benefiting you?** AWS Lambda has helped us solve our infrastructure cost problem. Before, we were paying for EC2 instances that sat idle for about 60% of the day. After moving to a pay-as-you-go model, we now pay only for the exact milliseconds our code is running, which has reduced our compute costs by nearly 40%. It has also improved our “Time to Market,” since we can deploy microservices in minutes without having to coordinate with an Ops team. ### 5. AWS Lambda: Effortless Serverless Scaling and Seamless AWS Integrations **Rating:** 5.0/5.0 stars **Reviewed by:** Shahzaib R. | Associate DevOps Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** February 02, 2026 **What do you like best about AWS Lambda?** AWS Lambda makes it easy to run code without managing servers. I like how it automatically scales based on demand and only charges for actual execution time, which helps reduce infrastructure cost. It integrates very well with other AWS services like API Gateway, S3, SQS, and DynamoDB, making it simple to build event-driven architectures. Deployment is fast, and for microservices or background jobs it saves a lot of operational overhead compared to managing EC2 instances. **What do you dislike about AWS Lambda?** Cold starts can sometimes impact performance, especially for VPC-based or larger functions. **What problems is AWS Lambda solving and how is that benefiting you?** AWS Lambda removes the need to provision, manage, and scale servers for running application logic. Instead of maintaining EC2 instances, patching OS, and handling auto-scaling, Lambda lets us focus only on writing code. It’s especially useful for handling event-driven workloads like API backends, file processing from S3, background jobs, and integrations between services. ### 6. Effortless Scaling and Cost Savings with AWS Lambda **Rating:** 5.0/5.0 stars **Reviewed by:** Gagan G. | Application Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** December 15, 2025 **What do you like best about AWS Lambda?** AWS Lambda's serverless scaling handled our 10k req/sec spikes perfectly, cutting costs 60% vs. EC2. Quick Python setup, seamless DynamoDB integration. Cold starts fixed with concurrency; minor timeout limits.​ Pros: Auto-scale, pay-per-use. Cons: VPC latency. Highly recommend! **What do you dislike about AWS Lambda?** AWS Lambda has notable limitations like cold starts that delay initial function invocations. The 15-minute execution timeout restricts longer-running tasks. Main Drawbacks Monitoring can feel fragmented without third-party tools, complicating debugging in complex apps. VPC integration adds latency and setup overhead. Vendor Lock-in Heavy reliance on AWS services reduces portability to other clouds. Deployment package size limits (250 MB unzipped) hinder large dependencies. **What problems is AWS Lambda solving and how is that benefiting you?** AWS Lambda solves serverless compute challenges by eliminating server provisioning, management, and scaling needs.​ Core Problems Addressed It handles infrastructure overhead, allowing focus on code for faster development cycles. Automatic scaling manages traffic spikes without manual intervention.​ Key Benefits Pay-per-use pricing cuts costs for idle time, while built-in high availability boosts reliability. This accelerates innovation and reduces operational burden.​ ### 7. Cost-Effective Serverless Execution with AWS Lambda **Rating:** 4.5/5.0 stars **Reviewed by:** Subrajit B. | Deputy Manager, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** February 11, 2026 **What do you like best about AWS Lambda?** I like most about the AWS lambda is . 1. It'server less execution means no need to provision or manage server . 2.This functions run only on when triggered(s3upload,API gateway request) . 3. cost effective , we need to pay only for the compute time. **What do you dislike about AWS Lambda?** Dislike about AWS Lambda are 1. Slow start, functions are takes extra time during initialization . 2.Long time execution limits . 3.Complex in debugging the functions . **What problems is AWS Lambda solving and how is that benefiting you?** Main problems it solves . 1.Server management overhead : no patching ,provisioning, scaling tension because of lambda function . 2.It resolves the scalability challenges on more load it scale sit self . 3.Cost efficiency - we need to pay only for it's computation . ### 8. Effortless Serverless Computing with Seamless AWS Integration **Rating:** 5.0/5.0 stars **Reviewed by:** Manil G. | Software engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** December 02, 2025 **What do you like best about AWS Lambda?** AWS Lambda is easy to use and simple to implement, especially for event-driven workflows. It integrates seamlessly with other AWS services, which makes building automation and serverless APIs very smooth. We use it frequently for scheduled jobs and lightweight backend tasks. The feature set is strong, with support for layers, versioning, and multiple runtime options. Customer support is decent, backed by solid documentation, although response times can vary. Overall, Lambda is a reliable and efficient serverless compute option. **What do you dislike about AWS Lambda?** Cold starts can be frustrating at times, and debugging or monitoring distributed serverless functions is harder compared to traditional applications. **What problems is AWS Lambda solving and how is that benefiting you?** AWS Lambda helps us eliminate server management for small services and automation tasks. It solves the problem of scaling and infrastructure overhead by automatically handling load, letting us focus only on the code. It’s especially useful for scheduled jobs, event-driven workflows, and API backends, which has reduced our operational effort and overall costs. ### 9. AWS Lambda Takes the Operational Heavy Lifting Off Your Plate **Rating:** 5.0/5.0 stars **Reviewed by:** Himanshi M. | Team lead software engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 02, 2026 **What do you like best about AWS Lambda?** AWS handles all the operational heavy lifting, including provisioning, patching, OS maintenance, and capacity management.You are only charged for the actual time your code executes, billed in 100-millisecond increments.Lambda functions are easily triggered by a wide variety of events from over 200 other AWS services.Lambda runs your code on a highly available compute infrastructure and manages fault tolerance across multiple Availability Zones, ensuring high resilience without extra effort.This allows developers to focus entirely on writing application logic. **What do you dislike about AWS Lambda?** Functions have a maximum execution time of 15 minutes, limiting their use for heavy, long-running batch jobs.Because code runs in a managed, ephemeral environment, attaching debuggers is impossible. Local testing is difficult to mirror properly.Leveraging framework tools (e.g., SAM, Serverless Framework) helps manage configuration and deployment, though it doesn't solve the core debugging issues.Unlike a persistent server, Lambda creates a new environment for concurrent requests. **What problems is AWS Lambda solving and how is that benefiting you?** Lambda scales horizontally in response to incoming events. Whether you have one request or thousands per second, the service creates new execution environments to handle the load instantly without manual configuration.Unlike traditional servers (EC2) where you pay for uptime regardless of usage, Lambda bills only for actual execution time rounded to the nearest millisecond.Triggering a welcome email whenever a new user is added to a database.Replacing traditional cron jobs with scheduled serverless functions for automated backups or reports. ### 10. Effortless Serverless Computing with AWS Lambda **Rating:** 4.5/5.0 stars **Reviewed by:** PRANSHU R. | Associate Software Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 29, 2026 **What do you like best about AWS Lambda?** I love that AWS Lambda lets us run our code without managing servers, making it an ideal choice for creating serverless services. Being a full-stack developer, it helps me build scalable backends and automate database queries efficiently. The ability to pay only for what I use is fantastic as it reduces costs and means I am only charged when my code is running. This 'pay as you use' model is preferred because it saves time on backend maintenance and lets us focus resources on more important tasks. The ease of integrating AWS Lambda with other services like S3 and API Gateway is a big plus for me. Additionally, setting it up was quite easy, thanks to the ample technical documents and videos available for learning. **What do you dislike about AWS Lambda?** We can't use some other services alongside AWS Lambda like Azure or Google Cloud in a seamless way. The cold start takes a while to initialize. **What problems is AWS Lambda solving and how is that benefiting you?** I use AWS Lambda to create a serverless service, running code without server management. It helps build scalable backends, automates database queries, and processes data. Its pay-as-you-use model cuts costs, and fast deployment saves time, allowing integration with services like S3 or API Gateway. ## AWS Lambda Discussions - [What is the best way to test locally without additional frameworks like serverless, SAM or Chalice?](https://www.g2.com/discussions/what-is-the-best-way-to-test-locally-without-additional-frameworks-like-serverless-sam-or-chalice) - 1 comment, 1 upvote - [What is AWS Lambda used for?](https://www.g2.com/discussions/what-is-aws-lambda-used-for) - 3 comments - [Is AWS lambda a container?](https://www.g2.com/discussions/is-aws-lambda-a-container) - 3 comments - [What is AWS Lambda built on?](https://www.g2.com/discussions/what-is-aws-lambda-built-on) - 2 comments - [How does AWS Lambda work?](https://www.g2.com/discussions/how-does-aws-lambda-work) - 2 comments ## AWS Lambda Integrations - [Amazon API Gateway](https://www.g2.com/products/amazon-api-gateway/reviews) - [Amazon CloudWatch](https://www.g2.com/products/amazon-cloudwatch/reviews) - [Amazon DynamoDB](https://www.g2.com/products/amazon-web-services-aws-amazon-dynamodb/reviews) - [Amazon EC2](https://www.g2.com/products/amazon-ec2/reviews) - [Amazon Elastic Container Registry (ECR)](https://www.g2.com/products/amazon-elastic-container-registry-ecr/reviews) - [Amazon EventBridge](https://www.g2.com/products/amazon-eventbridge/reviews) - [Amazon Kinesis Data Streams](https://www.g2.com/products/aws-amazon-kinesis-data-streams/reviews) - [Amazon Relational Database Service (RDS)](https://www.g2.com/products/amazon-relational-database-service-rds/reviews) - [Amazon Simple Email Service (Amazon SES)](https://www.g2.com/products/amazon-simple-email-service-amazon-ses/reviews) - [Amazon Simple Notification Service (SNS)](https://www.g2.com/products/amazon-simple-notification-service-sns/reviews) - [Amazon Simple Queue Service (SQS)](https://www.g2.com/products/amazon-simple-queue-service-sqs/reviews) - [Amazon Simple Storage Service (S3)](https://www.g2.com/products/amazon-simple-storage-service-s3/reviews) - [AWS Amplify](https://www.g2.com/products/aws-amplify/reviews) - [AWS Glue](https://www.g2.com/products/aws-glue/reviews) - [AWS IoT](https://www.g2.com/products/aws-iot/reviews) - [AWS Step Functions](https://www.g2.com/products/aws-step-functions/reviews) - [Cargo Operations Management System](https://www.g2.com/products/cargo-operations-management-system/reviews) - [Datadog](https://www.g2.com/products/datadog/reviews) - [Docker](https://www.g2.com/products/docker-inc-docker/reviews) - [Google Analytics](https://www.g2.com/products/google-analytics/reviews) - [Jenkins](https://www.g2.com/products/jenkins/reviews) - [Okta](https://www.g2.com/products/okta/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [TensorFlow](https://www.g2.com/products/tensorflow/reviews) - [Windows 11](https://www.g2.com/products/windows-11/reviews) - [Xurrent IMR](https://www.g2.com/products/xurrent-imr/reviews) ## AWS Lambda Features **Development** - Application Deployment - Development Tools - Development Environment - Language Support - Testing **Database** - Database Management - Analytics - Auto Scaling - Backup / Recovery - Storage **Infrastructure** - Networking - Virtual Machines - Security ## Top AWS Lambda Alternatives - [DigitalOcean](https://www.g2.com/products/digitalocean/reviews) - 4.6/5.0 (729 reviews) - [Red Hat OpenShift](https://www.g2.com/products/red-hat-red-hat-openshift/reviews) - 4.5/5.0 (289 reviews) - [Google App Engine](https://www.g2.com/products/google-app-engine/reviews) - 4.1/5.0 (191 reviews)