AWS Lambda Reviews & Product Details

What I like best about AWS Lambda is how it simplifies development by removing the need to manage servers—just write the function, set the trigger, and it runs when needed. It’s incredibly easy to implement and integrates smoothly with other AWS services like S3, DynamoDB, and API Gateway, which makes building complex workflows feel intuitive. The number of features available is impressive, and I find myself using it frequently for automation and event-driven tasks. Customer support has been generally helpful, especially through documentation and forums, though direct support could be more responsive at times. Overall, Lambda strikes a great balance between ease of use, powerful functionality, and scalability. Review collected by and hosted on G2.com.

One thing I dislike about AWS Lambda is the cold start latency, especially when using certain runtimes or when functions aren't invoked frequently—it can slow down response times noticeably. Debugging can also be a bit tricky since the environment is abstracted and logs are the main way to trace issues. While integration with other AWS services is strong, it sometimes feels like you're locked into the AWS ecosystem, which can limit flexibility. The limits on execution time and memory can be restrictive for more complex workloads, and managing deployments across multiple environments can get cumbersome without additional tooling. Lastly, while customer support is available, getting timely, hands-on help often requires a premium support plan. Review collected by and hosted on G2.com.

I just give it my code, and it handles the rest.

It is fast to develop.

Most servers cost money even when they are doing nothing. Lambda is different: if your code runs for two seconds, you only pay for those two seconds. Review collected by and hosted on G2.com.

It kills the process in a short period of time, like 15 minutes, I think. Review collected by and hosted on G2.com.

AWS Lambda makes' me feel like i am writing pure logic without worrying about servers, scaling, or infrastructures. I just upload the functions, set the trigger, and it works daily with ease for automation, API endpoints and backend workflows, whether it runs once a day or a million times, the auto scaling and pay as you go model feel incredibly efficient Review collected by and hosted on G2.com.

A more virtual to trace functions would help Review collected by and hosted on G2.com.

extremely easy to setup and maintain, lots of runtime options, super fast as NodeJS backend for Progressive Web Apps Review collected by and hosted on G2.com.

cost at scale requires to carefully configure function specs and concurrency settings Review collected by and hosted on G2.com.

I love AWS Lambda for its ease of use, as it allows me to focus solely on writing and deploying my API code without the hassle of managing infrastructure. This feature is incredibly useful for streamlining development and deployment processes, eliminating the traditional need to spin up servers or virtual machines. Additionally, I appreciate the remarkable speed of AWS Lambda compared to traditional API deployments. This efficiency significantly enhances my workflow, making API delivery faster and more reliable. Review collected by and hosted on G2.com.

I find the pricing for AWS Lambda somewhat high. It would be beneficial if there was a less expensive tier for lower memory usage. Review collected by and hosted on G2.com.

What I like best about AWS Lambda is its serverless simplicity. I can run code without managing servers, scale automatically based on demand, and pay only for execution time. It integrates seamlessly with AWS services, enabling faster development, reduced operational overhead, and efficient event-driven architectures. Review collected by and hosted on G2.com.

What I like less about AWS Lambda, but understand positively, is the execution and runtime limitations. Cold starts, timeout limits, and debugging complexity encourage better code optimization and modular design, ultimately pushing me toward more efficient, scalable, and well-architected serverless solutions. Review collected by and hosted on G2.com.

In my current role as a QA Test Engineer at Aarete Technosoft Pvt. Ltd., we’ve integrated AWS Lambda into our automation framework to support Selenium-based UI testing. The best part about using Lambda is that it completely eliminates the need for maintaining dedicated test servers. No EC2 lifecycle, no infrastructure stress — just lightweight, serverless execution.

One major win for us was the ability to run multiple test cases in parallel by triggering separate Lambda functions for different test groups. We’ve integrated this into our Jenkins pipeline, so once a new build is deployed to the QA environment, Lambda is automatically triggered via API Gateway to start our automation suite — no manual steps, faster feedback.

We’ve also packaged headless Chromium and Selenium scripts using Lambda Layers, making test execution efficient and cost-effective without spinning up EC2 instances.

After test runs, logs and reports are uploaded to Amazon S3, and another Lambda function processes them, pushing summarized data into CloudWatch for trend analysis and monitoring. This seamless flow has helped us speed up regression cycles and gain real-time test visibility. Review collected by and hosted on G2.com.

While AWS Lambda has added a lot of flexibility to our Selenium automation workflows, there are a few limitations I’ve observed in our project at Aarete Technosoft Pvt. Ltd. that impact the testing experience:

1.When a function hasn’t been invoked in a while, there’s a cold start delay. This is particularly noticeable in our CI/CD pipelines where fast feedback matters. Even a few extra seconds per function adds up during regression runs.

2.Since Lambda runs are headless and non-interactive, debugging flaky UI issues becomes harder without a live browser view. We rely entirely on logs and screenshots saved to S3.

3.Lambda’s 15-minute timeout can be a challenge for long-running Selenium suites, especially if a test involves waiting for backend jobs or heavy UI flows. Review collected by and hosted on G2.com.

Best and Cost effective serverless service. Can integrate with many service in AWS. Review collected by and hosted on G2.com.

Will be helpfull only when we use aws service. Tough to integrate 3rd party cloud services. Time limit can be increased for processing Review collected by and hosted on G2.com.

AWS Lambda delivers a fully managed compute service that automatically runs code in response to events, without requiring server provisioning or ongoing maintenance.

The event driven architecture supports integrations with services like S3, DynamoDB, API Gateway, SNS, and SQS, which simplifies building complex, scalable workflows.

Multiple programming languages are supported, including Python, Node.js, Java, Go, C#, and PowerShell, with deployment options for both .zip archives and container images.

Elastic scaling is inherent; the platform adjusts capacity instantly to handle workloads ranging from a few invocations daily to thousands per second. Performance remains consistent, and availability is managed by AWS.

Environment variables, layers for shared code, and versioning streamline application configuration and deployment. Security is robust, with granular IAM controls, code signing for production compliance, and options for VPC integration and file system access where needed.

Lambda SnapStart reduces cold start latency for Java functions, and response streaming enables efficient handling of large payloads in APIs and data processing. Review collected by and hosted on G2.com.

Lambda functions are stateless by design, so persistent local state requires integration with external storage services, adding architectural complexity.

Native monitoring tools are basic, and operational visibility often needs supplementation with third party solutions.

Cost optimization requires attention to avoid unexpected charges from irregular usage patterns. Review collected by and hosted on G2.com.

One of the advantages is that it supports a wide range of programming languages, making it easier to run various applications. Additionally, the cost of invoking workflows that need to be triggered is relatively low. It also offers seamless integration with several other AWS services, such as S3, EventBridge, and API Gateway. Review collected by and hosted on G2.com.

For programs that require secrets, it is necessary to read parameters from SSM each time, which causes the Lambda response to be relatively slow. Review collected by and hosted on G2.com.