AWS Lambda Reviews & Product Details

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.

Seller

Amazon Web Services (AWS)

Discussions

AWS Lambda Community

Solution Type

Best-of-Breed

Overview by

John Miranda (Digital Marketing Specialist at Amazon Web Services)

Value at a Glance

Averages based on real user reviews.

Time to Implement

2 months

Return on Investment

10 months

View More Pricing Information

Top-Rated Alternatives

View All Alternatives

User Insights

Average based on 1055 real user reviews.

Implementation Time

2 months

Perceived Cost

$$$$$

AWS Lambda Integrations

(38)

Integration information sourced from real user reviews.

Show More Integrations

AWS Lambda Reviews FAQs

Generated using AI

Last updated: Nov 04, 2026

What is AWS Lambda, and what problem is it built to solve?

AWS Lambda is a serverless compute service for running code in response to events, without requiring teams to provision or maintain servers. It is used for workloads such as automation, APIs, scheduled tasks, and event-driven processing.

What company sizes and industries is AWS Lambda the best fit for?

Positive experiences are represented across small businesses, mid-market organizations, and enterprises, with industry representation especially visible in software and IT-related fields. The reviewer-reported segments include:

Company size: Small businesses, mid-market organizations, and enterprises.
Software and IT: Computer Software and Information Technology and Services.
Financial services: Financial Services and Banking.
Other represented industries: Computer & Network Security, Telecommunications, Education Management, and Health Care.

How long does it take to implement AWS Lambda across a team?

Implementation timelines range from less than a day to several months, with the shortest reported time the most common. The reported patterns include:

Time to go live	Relative frequency
Less than 1 day	Most common
Less than 1 month	Also frequently reported
1–3 months	Less common
3–6 months or longer	Occasionally reported

What customer support options does AWS Lambda provide, and how do users find the overall support experience?

Support is available through email/help desk, FAQs or forums, and a knowledge base. The experience can be helpful for documentation and onboarding, while access to timely, hands-on assistance may vary.

What is the experience like for teams switching to AWS Lambda from another tool?

Teams have moved workloads from platforms such as EC2, Azure Functions, Jenkins, and other server- or container-based setups to AWS Lambda. The change is often about avoiding server upkeep and scaling work, and paying for execution rather than keeping infrastructure running; Lambda is especially useful for event-driven automation and short tasks, while longer-running jobs or full CI/CD pipelines may remain on other tools.

What tools and platforms does AWS Lambda integrate with, and how do these integrations help users get more value from the product?

AWS Lambda offers 38 integrations, spanning AWS services as well as developer and business tools. Commonly named integrations fall into these groups:

Storage and databases: Amazon S3, DynamoDB, and RDS.
APIs and event workflows: API Gateway, EventBridge, Step Functions, SQS, and SNS.
Monitoring and delivery: CloudWatch, Jenkins, GitHub, and GitLab.
Data and external tools: Airtable and third-party databases or services.

These connections let teams trigger functions from events, process files or messages, connect APIs and databases, and automate deployments and operational tasks.

What features or capabilities could make AWS Lambda even more useful?

The most useful improvements would make Lambda easier to troubleshoot and more accommodating for workloads with demanding performance or execution needs. Recurring requests include:

Reduce cold-start delays, particularly for functions that run infrequently or serve latency-sensitive applications.
Improve debugging, tracing, and monitoring visibility across distributed functions and connected services.
Offer more flexibility for long-running jobs that exceed current execution limits.
Simplify local testing, dependency and package management, and deployment workflows.

G2 reviews are authentic and verified.

Here's how.

Nidal S.

Senior DevOps Engineer

Mid-Market (51-1000 emp.)

4/28/2026

"Effortless Scaling and Cost-Efficient Event-Driven Workloads with AWS Lambda"

5/5

What do you like best about AWS Lambda?

From my experience, what I like most about AWS Lambda is that it removes the need to manage infrastructure while automatically scaling with demand, integrates seamlessly with other AWS services, and provides a cost-efficient way to build and run event-driven workloads. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

The limits:

- The size limit of 250 MB.

- The concurrency limit issue.

- The limited supported programming languages Review collected by and hosted on G2.com.

Sayed M.

Consultant

Mid-Market (51-1000 emp.)

5/23/2026

"Simple, Flexible, and Cost-Effective Serverless Scaling with AWS Lambda"

5/5

What do you like best about AWS Lambda?

I like its simplicity and flexibility for running applications without having to manage servers. It scales automatically based on traffic, which makes deployments faster and more efficient. The pay-as-you-use pricing model also feels cost-effective, since you only pay for the actual execution time. Another big advantage is how smoothly it integrates with other AWS services, making it easier to build event-driven, highly automated workflows while keeping infrastructure management to a minimum. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

At the moment, I don’t have any major concerns with AWS Lambda. Review collected by and hosted on G2.com.

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

AWS Lambda removes the need for server maintenance, which makes deployment simpler and faster.

It also scales automatically with changing workload demands, helping maintain reliable performance.

With its pay-per-use pricing model, I can avoid paying for unnecessary infrastructure and keep costs under control. Review collected by and hosted on G2.com.

Vikas N.

System Engineer

Enterprise (> 1000 emp.)

5/26/2026

"Serverless Efficiency with Seamless AWS Integration"

4/5

What do you like best about AWS Lambda?

I like AWS Lambda's serverless architecture and automatic scaling. It's great how it seamlessly integrates with AWS services, which significantly reduces infrastructure overhead. This really speeds up the backend development and deployment. AWS Lambda is effective because it eliminates the need to manage and maintain servers for backend applications. I appreciate how it automatically handles scaling, infrastructure management, and the execution of code based on events, reducing operational effort and infrastructure costs. It also enables fast deployment and development. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

One of the limitations I've faced is the cold start latency for some workloads, and the complexity that can arise when debugging serverless applications. Review collected by and hosted on G2.com.

Muhammad Awais A.

Sr ICT Engineer

Information Technology and Services

Small-Business (50 or fewer emp.)

Originally submitted 1/24/2026

"True Zero-Administration Serverless Model That Lets Us Focus on Coding"

4/5

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Chandan D.

Staff Software Development Engineer Test

Information Technology and Services

Enterprise (> 1000 emp.)

1/14/2026

"Zero Server Management and Seamless Auto-Scaling with AWS Lambda"

4.5/5

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Shahzaib R.

Associate DevOps Engineer

Small-Business (50 or fewer emp.)

2/2/2026

"AWS Lambda: Effortless Serverless Scaling and Seamless AWS Integrations"

5/5

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. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Cold starts can sometimes impact performance, especially for VPC-based or larger functions. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Swapnil B.

Devops Engineer

Computer & Network Security

Enterprise (> 1000 emp.)

Originally submitted 7/24/2022

"Serverless computing made easy"

4.5/5

What do you like best about AWS Lambda?

It eliminates the need to have a physical server. It coneects apis effortlessly. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Pricing makes it a bit expensive but still the leader in its field. Review collected by and hosted on G2.com.

Keyur T.

Mobile app developer

Information Technology and Services

Small-Business (50 or fewer emp.)

4/29/2026

"Cost-Effective with Event-Based Scaling"

5/5

What do you like best about AWS Lambda?

I like using AWS Lambda because it's cost-effective with event-based triggers and offers fast servers. It's great that I don't need to panic about load since it automatically handles our cloud infrastructure's auto-scaling based on the traffic. The billing based on usage, especially for our website with time-based traffic, helps manage costs efficiently. Also, the initial setup was very easy, which was a plus. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

They don't have a cPanel, we need to do all using SSH and command line. I think they need to build a cPanel. Review collected by and hosted on G2.com.

Gagan G.

Senior Software Engineer

Mid-Market (51-1000 emp.)

12/15/2025

"Effortless Scaling and Cost Savings with AWS Lambda"

5/5

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! Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.