AWS Lambda Reviews & Product Details

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

Cold starts can be frustrating at times, and debugging or monitoring distributed serverless functions is harder compared to traditional applications. Review collected by and hosted on G2.com.

1. A serverless service, which can be used for automating the work. ex: volume backup, scheduling the stopping of unused servers

2. Implementation is easy; creating the function is very easy. and it lets u run code according to your coding language

3. As a user, we do not need to maintain; by default, AWS will manage.

4. Triggers can be added for the invocation of other services, such as s3, and event driven process

5. it reduces the human efforts for getting the reports from databases as well.

6. one function can be used for many types of work. Support for lambda is quick Review collected by and hosted on G2.com.

There are limitations that lambda can only execute for 15 min, if there is any function that needs to operate above 15 min then lambda is not suitable service. also the memory , disck space are limited only, thes which makes few operations tough Review collected by and hosted on G2.com.

Code is completely free and I have trial it with not require upgrade, it can be start, everytime, I can try to upload code with ZIP and image, it like AI and it will be complete code.

AWS Lambda shines with its ability to run code without provisioning or managing servers, making deployment incredibly fast and efficient. It automatically scales based on demand, so you only pay for what you use—down to the millisecond. Plus, its seamless integration with other AWS services like S3, DynamoDB, and API Gateway makes building complex applications surprisingly smooth. Review collected by and hosted on G2.com.

AWS Lambda can become expensive at scale, especially when functions are invoked frequently or run for extended durations. The cost model—based on number of requests and execution time—can be hard to predict, making budgeting tricky for complex applications. Additionally, integrating Lambda with other AWS services may incur extra charges, increasing the overall product cost beyond just the function itself. Review collected by and hosted on G2.com.

You can simply write your code and deploy it, as testing is straightforward. It's easy to connect to any runtime, and you can even trigger Lambda functions using SNS and EventBridge rules without much hassle. There's no need to manage a server—just attach an API Gateway, and you're set. Review collected by and hosted on G2.com.

What I dislike most is the cold start issue. In many of our applications, it leads to slow performance and occasionally causes errors when there are concurrent invocations. Review collected by and hosted on G2.com.

What I like most about AWS Lambda is how it completely removes the need to manage servers. You just focus on writing code, and it takes care of everything else—scaling, patching, provisioning. It’s incredibly efficient, especially for event-driven tasks like processing S3 uploads, reacting to database changes, or triggering workflows based on user actions. It also scales automatically, so whether you’re handling one request or a thousand, it just works without you needing to plan for capacity. Plus, the pay-as-you-go model means you're only charged for the time your code actually runs, which is great for keeping costs low. I also appreciate how well Lambda integrates with the rest of the AWS ecosystem—whether it's SQS, DynamoDB, or Step Functions, it all ties together seamlessly. It’s a powerful tool for building modern, scalable, and cost-effective applications. Review collected by and hosted on G2.com.

One of the main things I dislike about AWS Lambda is the **cold start latency**, especially when using certain runtimes like Java or when functions are in a VPC. That delay, even if it's just a couple of seconds, can be noticeable in user-facing applications. Another challenge is **limited observability** out of the box—while you can plug in tools like CloudWatch or X-Ray, it often takes extra effort to get clear visibility into performance and failures. Also, **debugging and testing locally** can be tricky, especially when dealing with event sources like API Gateway or DynamoDB streams. And while the simplicity is great for small functions, managing a large number of Lambdas can get messy fast—things like versioning, environment variables, permissions, and deployment pipelines need to be tightly organized. Finally, the **timeout and memory limits** make Lambda unsuitable for certain long-running or resource-heavy workloads, so you have to design around those constraints. Review collected by and hosted on G2.com.

- I like that I can write a specific function or unit of code which is focus on performing a single task

- You only pay for the amount of time you run it and this encourages you to optimize your code in terms of time and space complexities to save money

- Simple to use and setup and execute once you get the hang of it

- Can be used to re-write the origin of your CloudFront Distribution as well and allows the static hosting using S3

- I believe that lambda is at the core of AWS services and can be helpful in accomplishing many tasks across a range of services

- It can be used to create a range of microservices too Review collected by and hosted on G2.com.

- If you do not optimize the code, you may end up paying more

- Supports limited languages in which you can write the lambda Review collected by and hosted on G2.com.

The ease of deployment of an AWS Lambda function is amazing. I can literally have vs code editor in AWS Lambda for editing my code. This makes my testing and deployment very easy and efficient. I do the testing in the cloud IDE itself. Review collected by and hosted on G2.com.

The limitation of 15 minutes becomes sometimes annoying because I use lambda functions for processing data which sometimes is in GBs and hence 15 minutes are not enough. Review collected by and hosted on G2.com.

What I like best about AWS Lambda is how easy it makes running code without worrying about managing servers. I can just upload my code, set up a trigger, and Lambda automatically scales to handle anything I throw at it—whether it’s a few requests or thousands, all without me having to do any infrastructure work. It’s fast, simple, and lets me focus on building, not maintaining. Review collected by and hosted on G2.com.

One thing I dislike about AWS Lambda is that it has some limitations that can be frustrating, like the 15-minute execution time limit and occasional cold start delays, which can slow things down if your function hasn’t run in a while. There are also restrictions on memory, storage, and payload size, so it’s not great for big or long-running tasks. Plus, since Lambda is so tightly tied to AWS, moving your application elsewhere can be tricky, and debugging can sometimes be harder than in traditional setups. Review collected by and hosted on G2.com.

I’ve been using AWS Lambda for some time, and what I appreciate most is not having to deal with server management. It simply works, scaling automatically when necessary, and I only pay for the actual runtime of my code. Setting up triggers from S3 or DynamoDB is extremely convenient and saves a significant amount of deployment time. Honestly, it makes developing small applications or microservices much easier, as I can concentrate on writing code rather than handling infrastructure. Review collected by and hosted on G2.com.

Lambda has a maximum timeout of 15 minutes, which makes it unsuitable for long-running tasks. Review collected by and hosted on G2.com.

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.