starter.wikiSearch⌘K

AWS event-driven functions

AWS Lambda Functions

AWS-native event-driven Functions with managed scaling, runtime and package constraints, IAM, and service integrations.

Visit official site

Editorial verdict

Choose Lambda Functions for AWS-native event-driven work that fits the stable Functions limits and benefits from managed scaling and service integration.12

Best for

  • AWS event-source integrations
  • Short-lived handlers that fit Functions limits
  • Teams aligned with AWS IAM, networking, logs, and service APIs
12

Not ideal for

  • Persistent servers or arbitrary containers
  • Durable multi-step workflows requiring independent run state
  • Unmodeled concurrency, network, log, transfer, or downstream service cost
12
Main trade-off

Deep AWS integration and managed event scaling are gained with function limits, cold-start/concurrency behavior, AWS coupling, and adjacent service cost.12

Product boundary

Whether an AWS event workload fits the stable Lambda Functions runtime, quota, packaging, and billing model.

This Tool covers stable Lambda Functions only; Lambda-compatible container images are packages, not arbitrary container hosting, and newer Lambda surfaces require separate verification.12

For: AWS teams deploying short-lived request or event handlers

  • Execution exceeds the stable Functions limits.
  • A persistent service or arbitrary container is required.
  • Durable workflow history is the actual need.

Why teams consider AWS Lambda Functions

  • AWS eventsFunctions integrate with AWS event sources.12
  • Managed scalingAWS manages function instance scaling within quotas.12
  • Runtime choiceManaged runtimes and Lambda-compatible images support bounded package routes.12

Pricing

Requests plus memory-duration for Functions, with separate optional capacity, logs, network, streaming, and adjacent service costs.2

Stable Functions

Request and duration usage

Model region, architecture, requests, memory, duration, concurrency, logs, network, and event sources.2

Free tier
1 million requests and 400,000 GB-seconds at verification2
Duration boundary
15-minute Functions maximum at verification2
Pricing checked View official pricing

AWS Lambda Functions vs alternatives

Cloudflare Workers

Choose when
Choose a web-platform isolate and Cloudflare bindings.
Compared with AWS Lambda Functions
Node and resource behavior differ from Lambda.45

Google Cloud Run

Choose when
Choose a managed container service/function route.
Compared with AWS Lambda Functions
Google Cloud service and instance semantics replace AWS event integration.67

Amazon ECS

Choose when
Choose long-running containers and explicit capacity.
Compared with AWS Lambda Functions
Container service operations are larger than a function.89

Resources and sources

Official product, policy, and pricing

  • AWS Lambda Functions overview
    Open
  • AWS Lambda pricing
    Open
  • AWS Lambda quotas
    Open
  1. 1
    AWS Lambda Functions overview

    Amazon Web Services · Accessed Official

  2. 2
    AWS Lambda pricing

    Amazon Web Services · Accessed Official

  3. 3
    AWS Lambda quotas

    Amazon Web Services · Accessed Official

  4. 4
    Cloudflare Workers documentation

    Cloudflare · Accessed Official

  5. 5
    Workers platform limits

    Cloudflare · Accessed Official

  6. 6
    What is Cloud Run

    Google Cloud · Accessed Official

  7. 7
    Cloud Run resource model

    Google Cloud · Accessed Official

  8. 8
    Amazon ECS overview

    Amazon Web Services · Accessed Official

  9. 9
    ECS capacity option comparison

    Amazon Web Services · Accessed Official