1. [Home](https://www.g2.com/) 2. ... 3. [Cloud Platform as a Service (PaaS) Software](https://www.g2.com/categories/cloud-platform-as-a-service-paas) 4. [AWS Lambda](https://www.g2.com/products/aws-lambda/reviews) 5. [AWS Lambda Claims vs Evidence](https://www.g2.com/products/aws-lambda/claims-vs-evidence) # AWS Lambda Claims vs Evidence This page compares marketing claims that AWS Lambda makes on its own website with what real G2 users say in their reviews. Each claim's source link points to the page where it appeared. Claims are rated as follows: Supported when a clear majority of the reviewers who address it back it up, Disputed when a clear majority contradict it, and Mixed when reviewers are divided. Reviews that don't mention a claim are not counted. Last updated Sep 30, 2026 ## Claim: “Lambda runs your functions on fully managed infrastructure by default, with automatic scaling and pay-per-use pricing.” Supported by reviews. Relevant reviewers consistently report that Lambda removes the need to manage servers, scales automatically with demand, and charges based on actual execution or compute time, directly addressing the claim. - “What I like most about AWS Lambda is that I don’t have to worry about managing servers or infrastructure. I can just focus on writing and deploying my code, and Lambda automatically handles the scaling based on demand. It’s also convenient for building event-driven applications, and I like that I only pay for the compute time my functions actually use.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/13514466) - “AWS handles all the operational heavy lifting, including provisioning, patching, OS maintenance, and capacity management.You are only charged for the actual time your code executes, billed in 100-millisecond increments.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12295435) - “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.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12181098) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Run user- or AI-generated code in isolated sandboxes with full state retention and lifecycle control.” Disputed by reviews. Relevant reviewers describe Lambda as stateless and running in managed, ephemeral environments, with state requiring external services, which conflicts with the claim of full state retention. Reviews support running code, but do not establish full sandbox lifecycle control. - “Lambda functions are stateless by design, so they require external services for state management.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12129469) - “the session management for the database and other core layer which are not preserved but that issue is ok to live with” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12989560) - “Because code runs in a managed, ephemeral environment” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12295435) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Process streams, transform records, and fan out to downstream systems as data arrives.” Supported by reviews. Relevant reviewers describe Lambda processing and transforming continuous or streamed data, handling event-source ingestion, and supporting fan-out integrations with downstream AWS services. The evidence is consistently aligned with the claimed streaming, transformation, and fan-out workflow. - “Analyze and transform continuous data streams.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12713034) - “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” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12760532) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Lambda Functions handle the scaling, you handle the logic.” Supported by reviews. Relevant reviewers consistently report that Lambda automatically handles scaling and infrastructure management, allowing them to focus on writing application logic. - “I don’t have to worry about managing servers or infrastructure. I can just focus on writing and deploying my code, and Lambda automatically handles the scaling based on demand.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/13514466) - “It automatically scales based on demand, which makes it ideal for handling unpredictable workloads.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/13142695) - “No infrastructure management: You just deploy your function and AWS handles servers, scaling, and maintenance.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12723724) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Build multi-step, long-running workflows that can pause, wait for signals, retry on failure, and run for hours.” Disputed by reviews. Some reviewers describe event-driven workflows with built-in retry behavior, but multiple reviewers report a hard 15-minute execution limit and say Lambda is unsuitable for long-running jobs, conflicting with the claim that workflows can run for hours. - “retry behavior out of the box” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12896877) - “There are limitations that Lambda can only execute for 15 min; if there is any function that needs to operate for more than 15 min, then Lambda is not a suitable service.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/11920770) - “the 15-minute execution limit means Lambda isn't suitable for long-running jobs — for those, we still rely on ECS or Step Functions.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12910814) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Run code at any scale with zero infrastructure management.” Mixed support from reviews. Reviewers frequently report automatic scaling and no need to manage servers, including handling workloads from one to thousands of requests. However, other reviewers describe concurrency, memory, and 15-minute execution limits that make Lambda unsuitable for some heavy or long-running workloads, so the claim’s “at any scale” wording is not consistently supported. - “It scales automatically if 1 person uses my app or 10,000 persons Lambda handles it without me doing anything extra.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12181098) - “Automatic scaling: It scales instantly from zero to thousands of requests without configuration.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12723724) - “The memory is limited, so it isn’t really suitable for high-compute jobs like ML. There also seem to be limits on concurrent executions, which makes it harder to run multiple tasks at the same time.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12788238) - “Functions have a maximum execution time of 15 minutes, limiting their use for heavy, long-running batch jobs.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12295435) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Lambda Functions sits natively on Amazon Kinesis, Apache Kafka, Amazon SQS, and Amazon DynamoDB Streams, so you get sub-second processing without provisioning or tuning throughput.” Mixed support from reviews. Reviewers support Lambda’s native integrations with DynamoDB Streams, SQS, and Kinesis and its lack of server provisioning, but cold-start reports—including delays of a couple of seconds—undermine the claim of consistently sub-second processing. The reviews do not establish that throughput never requires tuning. - “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.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12896877) - “The cold start latency can be a challenge, especially for latency-sensitive automation tasks that aren't invoked frequently.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12910814) - “That delay, even if it's just a couple of seconds, can be noticeable in user-facing applications.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/11453128) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/) ## Claim: “Lambda MicroVMs launch and resume rapidly with per-tenant isolation, retain state across sessions, and pause automatically when idle so you only pay for active use.” Mixed support from reviews. Reviewers support the pay-for-active-use aspect, describing charges only for compute or invocations rather than idle compute. However, reviewers also report cold-start delays that undermine rapid resumption and state that Lambda is stateless, while per-tenant isolation is not meaningfully addressed. - “I only pay for the compute time my functions actually use.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/13514466) - “The pay-per-invocation pricing model means we're not paying for idle compute” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12910814) - “Cold starts can also be an issue for certain applications where quick response times are important.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/13514466) - “Lambda functions are stateless by design, so they require external services for state management.” [Read Full Review](https://www.g2.com/products/aws-lambda/reviews/12129469) Source: [https://aws.amazon.com/lambda/](https://aws.amazon.com/lambda/)