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.

Verified User in Computer Software

Enterprise (> 1000 emp.)

1/16/2026

"Efficient serverless compute with seamless AWS integration"

5/5

What do you like best about AWS Lambda?

AWS Lambda makes it easy to run code without managing servers, which significantly reduces operational overhead. Implementation is fast, especially when integrated with other AWS services like API Gateway, S3, and DynamoDB. It scales automatically, supports frequent use for event-driven workloads, and offers a strong set of features for building modern, serverless applications. The pay-per-use pricing model is efficient, and AWS documentation and support are reliable. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Debugging and monitoring can be challenging compared to traditional server-based applications, especially for complex workflows. Cold start latency can impact performance for certain use cases, and local development and testing are not always straightforward. While integration within AWS is excellent, portability outside the AWS ecosystem is limited. Review collected by and hosted on G2.com.

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

AWS Lambda solves the problem of managing and scaling infrastructure for lightweight and event-driven workloads. It enables faster development cycles, reduces infrastructure costs, and allows teams to focus on business logic instead of server management. This results in quicker deployments, improved scalability, and better resource efficiency. Review collected by and hosted on G2.com.

Jonathan Miguel C.

Senior Software Developer

Logistics and Supply Chain

Mid-Market (51-1000 emp.)

2/20/2026

"AWS Lambda: Easy to Use, Feature-Rich, and Simple to Integrate"

5/5

What do you like best about AWS Lambda?

AWS Lambda is easy to use and straightforward to implement. It also offers a lot of features and is easy to integrate with other services. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Lambda functions are stateless by design, so they require external services for state management. Also, if a function hasn’t been used for a long time, it may experience a cold start. Review collected by and hosted on G2.com.

Verified User in Computer Software

Small-Business (50 or fewer emp.)

3/30/2026

"Serverless Simplicity with Seamless AWS Integrations"

4.5/5

What do you like best about AWS Lambda?

What I like most about AWS Lambda is its serverless architecture, which removes the need to manage infrastructure. It lets me focus on writing and deploying code, without having to worry about provisioning, configuring, or maintaining servers.

Another big advantage is how smoothly it integrates with other AWS services such as S3, API Gateway, and CloudWatch. That integration makes it straightforward to build event-driven applications and automate workflows.

I also appreciate its scalability and cost efficiency. Lambda scales automatically based on demand and uses a pay-per-use model, so I’m only paying for the compute time I actually consume. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

One of the biggest drawbacks of AWS Lambda is cold-start latency, especially for functions that aren’t invoked often. This can introduce small delays in response times, which may affect performance for real-time applications.

Another limitation is execution time and resource constraints. Lambda functions have a maximum runtime and restricted memory/CPU options, which can make them a poor fit for long-running tasks or resource-intensive workloads.

Debugging and monitoring can also be challenging. Although CloudWatch provides logs, tracing and troubleshooting issues across multiple Lambda functions and connected services can quickly become complicated, particularly in distributed architectures.

Finally, managing dependencies and deployment packages can be somewhat cumbersome, especially as applications grow larger. Review collected by and hosted on G2.com.

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

AWS Lambda solves the problem of managing and scaling infrastructure for backend services. Traditionally, setting up servers, planning for scaling, and maintaining uptime takes significant effort and resources. Lambda reduces that overhead by letting my code run in a fully managed, serverless environment.

It also tackles the challenge of handling event-driven workloads efficiently. Rather than keeping services running continuously, functions are triggered only when needed (for example, on file uploads or API calls). This improves resource utilization and helps avoid unnecessary costs.

For me, this has led to faster development cycles and lower operational complexity. I can deploy small pieces of functionality quickly, automate workflows, and integrate services without worrying about infrastructure management. It also supports cost optimization because I only pay for actual execution time instead of paying for idle server capacity.

Overall, AWS Lambda lets me focus more on business logic and less on system maintenance, which improves both productivity and scalability. Review collected by and hosted on G2.com.

Bishnu M.

Senior Project Manager

Information Technology and Services

Enterprise (> 1000 emp.)

5/19/2026

"AWS Lambda Makes Serverless Simple with Auto-Scaling and Pay-as-You-Go Efficiency"

4.5/5

What do you like best about AWS Lambda?

I really like how AWS Lambda lets me run code without managing servers. The automatic scaling and pay‑as‑you‑go model make it simple and efficient to use. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

The only small downside is that debugging can be a bit tricky at times, especially with cold starts. It’s not a major issue, but something to be aware of. Review collected by and hosted on G2.com.

Malkinder S.

Staff engineer, CloudOps

Mid-Market (51-1000 emp.)

4/28/2026

"Easy setup , support multiple platform and coding languages"

4/5

What do you like best about AWS Lambda?

Lambda is serverless so there's no tension about compute and memory.

On demand pricing , means you pay as you go.

very minimal efforts to setup.

integration with python and other languages. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Timeout can be an issue sometime, not efficient for long running jobs. Review collected by and hosted on G2.com.

Verified User in Information Technology and Services

Mid-Market (51-1000 emp.)

4/30/2026

"Effortless ingestion of uncertain events and autoscalling when required"

4/5

What do you like best about AWS Lambda?

The most helpful thing about Lambda is its auto-scaling, since it can automatically scale up when there are more requests. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Sometimes there are batch jobs that run for more than 15 minutes, and Lambda has a 15-minute timeout. Because of that, Lambda becomes undesirable for heavy data processing. Review collected by and hosted on G2.com.

anand p.

Sr. Engineering Manager

Information Technology and Services

Enterprise (> 1000 emp.)

1/6/2026

"Effortless Scaling and Cost Savings with AWS Lambda"

5/5

What do you like best about AWS Lambda?

I love that I don’t have to worry about servers at all. I just write my code, upload it, and AWS runs it for me whenever it’s needed. It scales automatically if 1 person uses my app or 10,000 persons Lambda handles it without me doing anything extra. Plus, I only pay when the code actually runs, so it’s often cheaper than keeping a server running all the time. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

Sometimes there is a small delay the first time a function runs, which can be an issue for real-time apps. Also, you can’t control the underlying server or install custom system-level software Lambda works best when your code fits neatly into its model.

And debugging or monitoring can be trickier than a regular server, though tools like CloudWatch help. Review collected by and hosted on G2.com.

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

Lambda solves the problem of managing and scaling servers. Instead of spending time setting up, patching, or monitoring machines, I can focus on writing code that adds real value to the product. It’s great for tasks like processing files when they’re uploaded, handling web requests or running scheduled jobs. Review collected by and hosted on G2.com.

Javier C.

Full Stack developer

Education Management

Small-Business (50 or fewer emp.)

2/6/2026

"Serverless + AWS: Smooth Triggers, Effortless Deployment, and Reliable Autopayments"

5/5

What do you like best about AWS Lambda?

The serverless works perfectly with AWS. I use a lot of triggers, and they work perfectly with my code. You can focus on code and deployment without worrying about handling the rest of the code. My experience with payment has been good, with the run code of autopayment. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

When you use it a lot,it need time to start again and repsonse times also become slower Review collected by and hosted on G2.com.

shanavaz a.

Cloud Engineer

Information Technology and Services

Mid-Market (51-1000 emp.)

1/22/2026

"AWS Lambda removes the headache of managing servers."

5/5

What do you like best about AWS Lambda?

I like AWS Lambda because it runs code without managing servers scales automatically and you only pay when it runs. It also works smoothly with others AWS services, making development faster and easier.implementation is easy.i have use lambda in my most of use case. Review collected by and hosted on G2.com.

What do you dislike about AWS Lambda?

The debugging and monitoring can be harder compared to traditional servers and limited execution time. Review collected by and hosted on G2.com.