---
title: AWS Lambda Reviews
meta_title: 'AWS Lambda Reviews 2026: Details, Pricing, & Features | G2'
meta_description: Filter 1043 reviews by the users' company size, role or industry
  to find out how AWS Lambda works for a business like yours.
aggregate_rating:
  rating_value: 4.6
  review_count: 1043
  scale: '5'
date_modified: '2026-07-12'
parent_category:
  name: Development
  url: https://www.g2.com/categories/development
---

# 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:** 1,043
## 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 find AWS Lambda&#39;s **ease of use** exceptional, allowing quick implementation without the hassle of maintenance. (47 reviews)
- Users value the **seamless scalability** of AWS Lambda, enabling quick adaptation to varying workloads without infrastructure concerns. (35 reviews)
- Users value the **cost-effectiveness** of AWS Lambda, paying only for compute time and optimizing resource usage. (27 reviews)
- Users appreciate the **serverless architecture** of AWS Lambda, enabling scalable application development without infrastructure concerns. (23 reviews)
- Users appreciate the **seamless integration** of AWS Lambda with other AWS services, streamlining development and deployment processes. (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 AWS Lambda&#39;s **resource limitations** restrict its suitability for heavy workloads and large datasets. (36 reviews)
- Users find **difficult debugging** of AWS Lambda functions challenging due to complex monitoring and environment abstraction. (17 reviews)
- Users experience **slow performance** due to cold starts, leading to noticeable latency and limitations for heavy workloads. (13 reviews)
- Users report **lagging performance** with AWS Lambda, citing slow start times and execution limits that hinder efficiency. (10 reviews)
- Users note that AWS Lambda can be **expensive** compared to other cloud providers, especially with irregular 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 Simplicity: Easy Scaling and Pay-Per-Use with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Jeyaganapathy N. | CloudOps Engineer - Associate , Small-Business (50 or fewer emp.)

**Reviewed Date:** June 08, 2026

**What do you like best about AWS Lambda?**

The best part about AWS Lambda is that it allows you to run code without the need for managing servers. It automatically handles the scaling and execution which makes it very easy for event driven workloads.
Additionally, the pricing model is very low as we need to pay only for the compute time your code actually runs.

**What do you dislike about AWS Lambda?**

One thing that i disliked about AWS Lambda is the execution limit, which makes it less suitable for running long process. Debugging can also be slighty difficult compared to the tradition server rest all if fine

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda helps me reducing the cost required for compute task instead or running the server we can use lambda to run only when the trigger gets hit which allow you to pay only the execution of the code it is code based helps us to automate serveral task like starting or stop a server at particular time daily or delete some things over the shedule period. do particular action based on the triggered actions all type of automation is possible due to lambda

  ### 2. AWS Lambda Transformed Our Event-Driven Automation

**Rating:** 4.5/5.0 stars

**Reviewed by:** Bibhishan D. | QA Lead, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** June 02, 2026

**What do you like best about AWS Lambda?**

As a DevOps/SRE engineer, AWS Lambda has completely transformed how we handle event-driven automation.
The ability to trigger functions in response to AWS events — whether it's an S3 upload, an SNS notification, a CloudWatch alarm, or a DynamoDB stream — without provisioning or managing any servers is incredibly powerful.
The pay-per-invocation pricing model means we're not paying for idle compute, which has noticeably reduced our cloud costs.

**What do you dislike about AWS Lambda?**

The cold start latency can be a challenge, especially for latency-sensitive automation tasks that aren't invoked frequently.
While Provisioned Concurrency helps, it adds cost. Also, the 15-minute execution limit means Lambda isn't suitable for long-running jobs — for those, we still rely on ECS or Step Functions.
Debugging complex multi-function workflows can also get tricky without proper distributed tracing set up via X-Ray.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda has allowed our team to build scalable, event-driven automation pipelines without the overhead of managing dedicated infrastructure.
It has freed up our SRE team to focus on higher-value reliability work rather than babysitting servers. Overall, it's become a core part of our automation toolkit on AWS.

  ### 3. AWS Lambda Makes Serverless Automation Scalable, Reliable, and Cost-Efficient

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Transportation/Trucking/Railroad | Mid-Market (51-1000 emp.)

**Reviewed Date:** June 27, 2026

**What do you like best about AWS Lambda?**

What I like most about AWS Lambda is how easy it is to build and run serverless applications without worrying about managing infrastructure. We use it extensively for automation tasks, event-driven workflows, and integrations with other AWS services, and it has significantly reduced the operational overhead compared to maintaining dedicated servers.

The integration with services like Amazon S3, CloudWatch, EventBridge, API Gateway, SNS, and SQS is seamless, making it straightforward to build scalable workflows. The AWS Management Console is easy to navigate for creating and monitoring functions, while support for infrastructure as code through CloudFormation and Terraform makes deployments consistent and repeatable.

Performance is excellent for most workloads, with automatic scaling handling traffic spikes without any manual intervention. The pay-per-use pricing model is another major advantage since we only pay for actual execution time, making it a cost-effective solution for workloads that don't need to run continuously.

AWS also provides good documentation, examples, and monitoring tools, which makes onboarding relatively smooth for developers familiar with the AWS ecosystem. Features like Amazon CodeWhisperer and AI-assisted log analysis have also been helpful for speeding up development and troubleshooting, although they're complementary to Lambda rather than built into the service itself.

Overall, AWS Lambda has helped us build reliable, scalable, and cost-efficient applications while allowing the team to focus more on business logic instead of infrastructure management.

**What do you dislike about AWS Lambda?**

AWS Lambda works very well for most use cases, but there are a few areas that could be improved. Debugging distributed, event-driven applications can sometimes be challenging, especially when a function interacts with multiple AWS services. While CloudWatch logs are helpful, troubleshooting complex workflows can still take time.

Cold starts can occasionally introduce noticeable latency, particularly for infrequently invoked functions or larger deployments, although AWS has made improvements over the years. Managing environment variables, IAM permissions, and deployment packages can also become more complex as the number of functions grows.

The AWS Console is feature-rich, but navigating through different configuration pages can feel overwhelming for new users. Overall, these are manageable limitations, and they haven't outweighed the benefits of using Lambda for scalable, serverless applications.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda has helped us eliminate the need to provision and manage servers for many backend and automation tasks. We use it for processing events, automating operational workflows, scheduled jobs, and integrating different AWS services. This has simplified our architecture and reduced the time spent on infrastructure management.

One of the biggest benefits is that Lambda scales automatically based on demand, so we don't have to worry about capacity planning during traffic spikes. It has also reduced our cloud costs because we only pay when the code is executed, rather than keeping servers running 24/7.

From a development perspective, Lambda has enabled us to deliver new features and automation much faster. Tasks that previously required dedicated virtual machines can now be implemented as lightweight functions, making deployments simpler and maintenance easier. Overall, it has improved our team's productivity, reduced operational overhead, and allowed us to focus more on building solutions instead of managing infrastructure.

  ### 4. 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.

  ### 5. Simple and Efficient Serverless Computing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Navin N. | Devops engineer, Computer Software, Mid-Market (51-1000 emp.)

**Reviewed Date:** June 09, 2026

**What do you like best about AWS Lambda?**

What I like most about AWS Lambda is how easy it makes running applications without worrying about servers. It automatically scales based on demand, saves time on infrastructure management, and helps reduce costs because you only pay when your code runs. It integrates smoothly with other AWS services, making development much faster and simpler.

**What do you dislike about AWS Lambda?**

One thing I dislike about AWS Lambda is that debugging and troubleshooting can sometimes be challenging, especially for complex applications. Cold starts may also cause slight delays for infrequently used functions, and managing execution time limits can be restrictive for long-running workloads. However, for most use cases, the benefits outweigh these limitations.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the problem of managing and maintaining servers for running applications and backend processes. Instead of spending time on infrastructure, I can focus on writing code and delivering features. It automatically scales based on demand and follows a pay-per-use model, which helps reduce operational effort and costs. This allows me to develop and deploy applications faster while improving overall efficiency.

  ### 6. AWS Lambda: Seamless Event-Driven Automation with S3, CloudWatch, and API Gateway

**Rating:** 5.0/5.0 stars

**Reviewed by:** mani s. | data engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** May 26, 2026

**What do you like best about AWS Lambda?**

I frequently use AWS Lambda in our project. We mainly use it for event-driven automation in our workflow. The best part is that once files arrive in S3, we’ve set it up to trigger automatically. This then automates the validation process, which I like the most. On top of that, its integration with other AWS tools is fast.

**What do you dislike about AWS Lambda?**

I don’t have any major dislikes about AWS Lambda. Overall, it’s a good product and has worked well for me.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps solve problems like automating recovery and monitoring when workflow failures happen. For example, if some files don’t arrive at the expected time, AWS Lambda can trigger notifications and send alert messages so I can respond quickly.

  ### 7. Easy to Configure, Powerful Fan-Out Scaling, and Seamless AWS Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Dhaval C. | Senior Technical Architect, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 06, 2026

**What do you like best about AWS Lambda?**

It is easy to configure. It has lots of user controls like run time, timeout, source event, layers, and it is pay-as-you-go. It gives immense power for fan-out scaling. Also, it is compatible with lots of AWS native services and integrates well with them, like API Gateway, S3, SNS, SQS, CloudWatch, and many more

**What do you dislike about AWS Lambda?**

Lambda has an upper limit on runtime, so you will have to design your system accordingly. Also, debugging becomes quite messy because there will be many invocations happening simultaneously.

**What problems is AWS Lambda solving and how is that benefiting you?**

For us, separation of concern in case of event, Event-driven architecture,
we don't have to worry about infra, as it is already taken care of by AWS. It supports all major runtimes and is well-documented, so getting community or dedicated support is easy.

  ### 8. Well-Supported, Well-Documented Tool for Running Background Jobs on AWS

**Rating:** 5.0/5.0 stars

**Reviewed by:** Adam E. | Solutions Integration Engineer, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** May 20, 2026

**What do you like best about AWS Lambda?**

It is a very well supported tool that provides great infrastructure for running background jobs and tasks periodically. It has great support with other AWS services and is easy to run with a lot of great documentation.

**What do you dislike about AWS Lambda?**

I don’t like that the maximum function time is limited to 15 minutes. I really hope this can be increased, because it doesn’t always accommodate bigger jobs.

**What problems is AWS Lambda solving and how is that benefiting you?**

It is allowing us to deploy integrations and jobs that run periodically in an easy and lightweight manner. It provides a great way to set up these background functions without needing to delve into the setup or server configuration and is easy to troubleshoot and connect to other services such as S3 and Cloudwatch.

  ### 9. Native AWS Event Integrations That Make Shipping Microservices Fast

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 31, 2026

**What do you like best about AWS Lambda?**

The native, abstract integration with the AWS event ecosystem.
Lambda feels like the ultimate connective tissue. Rather than writing boilerplate polling logic or managing persistent connections, you get clean, out-of-the-box event mappings for S3 hooks, DynamoDB Streams, SQS queues, and Kinesis. Being able to write a tightly focused handler function and then let the platform handle upstream ingestion, batch sizing, and retry behavior out of the box completely changes how quickly you can ship decoupled microservices.

**What do you dislike about AWS Lambda?**

The most frustrating part of working with AWS Lambda, for me, is dealing with its architectural guardrails—especially cold starts and the strict 15-minute execution limit. For synchronous, user-facing APIs, a cold start can cause a noticeable latency spike, and it’s even worse when the function runs inside a VPC. That reality forces careful mitigation (like Provisioned Concurrency), but doing so undercuts the “scale-to-zero” cost benefit.

On top of that, the hard timeout means Lambda simply isn’t a fit for long-running batch jobs or continuous processing. You end up having to split work into more complex, decoupled Step Functions workflows or offload it to ECS/Fargate, which adds architectural complexity that feels unnecessary.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda removes a lot of the headache of undifferentiated heavy lifting by abstracting away server management, capacity planning, and the complexity of event-polling infrastructure. Rather than spending time provisioning VMs, tuning auto-scaling policies, or writing boilerplate code just to consume queues, Lambda serves as native, event-driven glue that automatically scales from zero to thousands of concurrent requests as traffic comes in. For developers, this means you can focus squarely on core business logic, ship changes faster, and optimize infrastructure spend with a true pay-per-use, millisecond-precision billing model—so you’re not paying for idle compute.

  ### 10. Effortless Scalability for Modern Backend Workloads

**Rating:** 4.0/5.0 stars

**Reviewed by:** Andrés M. | Front-End Development Analyst I, Small-Business (50 or fewer emp.)

**Reviewed Date:** April 30, 2026

**What do you like best about AWS Lambda?**

No infrastructure management: You just deploy your function and AWS handles servers, scaling, and maintenance.
Automatic scaling: It scales instantly from zero to thousands of requests without configuration.
Cost efficiency: You only pay for execution time, not idle server time.

**What do you dislike about AWS Lambda?**

Cold starts: Functions can have latency delays when they haven’t been used recently, which affects performance in time-sensitive apps.
Execution limits: There are strict timeouts (max runtime), memory constraints, and ephemeral storage limits, which make it unsuitable for long-running or heavy compute tasks.

**What problems is AWS Lambda solving and how is that benefiting you?**

olves the problem of having to manage, scale, and maintain servers for backend workloads. Traditionally, teams needed to provision infrastructure, handle scaling, apply updates, and keep servers running—even when idle. Lambda removes that entire operational layer by running code only when it’s needed.


## 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

- [View AWS Lambda pricing details and edition comparison](https://www.g2.com/products/aws-lambda/reviews/aws-lambda-review-13086427?section=pricing&secure%5Bexpires_at%5D=2026-07-13+11%3A17%3A43+-0500&secure%5Bsession_id%5D=62689671-e42f-4c17-b72a-8e02a0e60563&secure%5Btoken%5D=2e47b2bb3969755883af1885cdafa942132abf06a16a0853fe04047e71fc4fba&format=llm_user)
## AWS Lambda Integrations
  - [Airtable](https://www.g2.com/products/airtable/reviews)
  - [Amazon API Gateway](https://www.g2.com/products/amazon-api-gateway/reviews)
  - [Amazon Aurora](https://www.g2.com/products/amazon-aurora/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 DynamoDB Accelerator (DAX)](https://www.g2.com/products/amazon-dynamodb-accelerator-dax/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 QuickSight](https://www.g2.com/products/amazon-quicksight/reviews)
  - [Amazon Relational Database Service (RDS)](https://www.g2.com/products/amazon-relational-database-service-rds/reviews)
  - [Amazon S3 Glacier](https://www.g2.com/products/amazon-s3-glacier/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)
  - [Amazon Textract](https://www.g2.com/products/amazon-textract/reviews)
  - [AWS Batch](https://www.g2.com/products/aws-batch/reviews)
  - [AWS Fargate](https://www.g2.com/products/aws-fargate/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)
  - [Azure Ai Foundry](https://www.g2.com/products/azure-ai-foundry/reviews)
  - [Cargo Operations Management System](https://www.g2.com/products/cargo-operations-management-system/reviews)
  - [Coralogix](https://www.g2.com/products/coralogix/reviews)
  - [Datadog](https://www.g2.com/products/datadog/reviews)
  - [Docker](https://www.g2.com/products/docker-inc-docker/reviews)
  - [Elastic Stack](https://www.g2.com/products/elastic-stack/reviews)
  - [Google Analytics](https://www.g2.com/products/google-analytics/reviews)
  - [machine-learning in Python](https://www.g2.com/products/machine-learning-in-python/reviews)
  - [Okta](https://www.g2.com/products/okta/reviews)
  - [Oracle Database](https://www.g2.com/products/oracle-database/reviews)
  - [PagerDuty](https://www.g2.com/products/pagerduty/reviews)
  - [pandas python](https://www.g2.com/products/pandas-python/reviews)
  - [Python](https://www.g2.com/products/python/reviews)
  - [python sql](https://www.g2.com/products/python-sql/reviews)
  - [Salesforce Agentforce](https://www.g2.com/products/salesforce-agentforce/reviews)
  - [Slack](https://www.g2.com/products/slack/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 (738 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 (192 reviews)

