AWS Lambda
AWS Lambda is a serverless, event-driven compute service that lets you run code for virtually any type of application or backend service without provisioning or managing servers. Lambda runs your code on high-availability compute infrastructure and performs all of the administration of the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, and logging.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles AWS Lambda the way a machine reads it — 167 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AWS Lambda scores 65.6/100 (strong), with a separate agent-readiness read of 80/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile AWS Lambda
Each block below is one kind of artifact we hold for AWS Lambda. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AWS Lambda Extensions API
The Lambda Extensions API enables you to create extensions that integrate with the Lambda execution environment lifecycle. Extensions can run as companion processes alongside yo...
AWS Lambda Telemetry API
The Lambda Telemetry API lets you collect telemetry data directly from the Lambda execution environment. Extensions can subscribe to telemetry streams for platform telemetry, fu...
AWS Lambda Runtime API
The Lambda Runtime API enables you to use custom runtimes to run functions in any programming language. The runtime API provides an HTTP API for custom runtimes to receive invoc...
AWS Lambda Logs API
The Lambda Logs API enables extensions to subscribe to log streams generated by the Lambda platform, function code, and extensions within the execution environment, providing ac...
AWS Lambda Aliases API
Create named pointers to function versions with routing configuration
AWS Lambda Concurrency API
Manage reserved and provisioned concurrency settings for functions
AWS Lambda Event Source Mappings API
Map event sources such as Amazon SQS, Kinesis, and DynamoDB Streams to Lambda functions for automatic invocation
AWS Lambda Function URL API
Configure dedicated HTTPS endpoints for Lambda functions that can be invoked directly via HTTP
AWS Lambda Functions API
Create, configure, invoke, and manage Lambda functions
AWS Lambda Layers API
Manage Lambda layers that package libraries, custom runtimes, and other dependencies for sharing across functions
AWS Lambda Tags API
The Tags API from AWS Lambda — 1 operation(s) for tags.
AWS Lambda Versions API
Publish and manage immutable function versions
Scroll within the panel for all 12 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
AWS Lambda API
OPEN COLLECTIONArazzo Workflows 13
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
AWS Lambda Release a Version Behind an Alias
Publish a version, then either move an existing alias onto it or create the alias if this is the first release.
ARAZZOAWS Lambda Shift Canary Traffic Across Two Versions
Read an alias, split its invocations between the current version and a canary version by weight, and read the routing back to confirm it took.
ARAZZOAWS Lambda Deploy a Function and Verify It Runs
Create a Lambda function from an S3 deployment package, wait for it to become Active, then invoke it once to prove it runs.
ARAZZOAWS Lambda Wire an Event Source to a Function
Confirm the target function exists, create an event source mapping onto a queue or stream, and poll until Lambda actually starts polling it.
ARAZZOAWS Lambda Audit a Function's Versions, Aliases, and Event Sources
Walk the account's functions, then drill into one to inventory its configuration, published versions, aliases, and attached event sources.
ARAZZOAWS Lambda Tear a Function Down in Dependency Order
Detach the event sources and the public URL that outlive a function, then delete the function and all its versions and aliases.
ARAZZOAWS Lambda Expose a Function Over an HTTPS Function URL
Confirm a function is Active, give it a dedicated HTTPS endpoint with an explicit auth type and CORS policy, and read the URL back.
ARAZZOAWS Lambda Find a Compatible Layer Version to Attach
Filter the account's layers by runtime and architecture, list the versions of a chosen layer, and resolve one to the exact ARN a function needs.
ARAZZOAWS Lambda Warm a Release with Provisioned Concurrency
Publish a version, point an alias at it, allocate provisioned concurrency to that alias, and wait until the environments are actually READY.
ARAZZOAWS Lambda Publish a Layer Version and Attach It to a Function
Publish a shared dependency layer from S3, verify the version, attach it to a function, and wait for the configuration update to settle.
ARAZZOAWS Lambda Cap a Function with Reserved Concurrency
Read a function's current concurrency reservation, set a ceiling on its simultaneous executions, and confirm the value Lambda stored.
ARAZZOAWS Lambda Tag a Function for Cost Allocation
Resolve a function name to its ARN, apply cost-allocation and ownership tags, and read the tags back to confirm the merge.
ARAZZOAWS Lambda Ship New Code and Cut an Immutable Version
Upload new function code, wait for the update to settle, smoke-test $LATEST, and publish an immutable version guarded by the code hash.
ARAZZOScroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
aws-lambda-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aws Lambda Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Aws Lambda Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Serverless Compute
Run code without provisioning or managing servers, paying only for the compute time consumed.
Event-Driven Execution
Automatically trigger functions from over 200 AWS services and SaaS applications via event source mappings.
Auto Scaling
Automatically scale from zero to thousands of concurrent executions in response to incoming events.
Function URLs
Dedicated HTTPS endpoints for Lambda functions that can be invoked directly without API Gateway.
Lambda Layers
Package shared libraries, custom runtimes, and dependencies as layers reusable across multiple functions.
Provisioned Concurrency
Pre-initialize function instances to reduce cold start latency for latency-sensitive workloads.
SnapStart
Improve startup performance for Java functions by caching initialized snapshots of the execution environment.
Lambda Extensions
Integrate monitoring, observability, and security tools directly into the Lambda execution environment.
Container Image Support
Package and deploy Lambda functions as container images up to 10 GB in size.
Graviton2 Support
Run functions on ARM-based AWS Graviton2 processors for better price-performance.
Scroll within the panel for all 10 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
AWS Lambda Event Triggers
AWS Lambda integrates with other AWS services to invoke functions in response to events. Lambda functions can be triggered by event sources including Amazon S3, Amazon DynamoDB ...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aws Lambda Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 35
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AliasConfiguration
JSON SCHEMAAliasRoutingConfiguration
JSON SCHEMACors
JSON SCHEMACreateAliasRequest
JSON SCHEMACreateEventSourceMappingRequest
JSON SCHEMACreateFunctionRequest
JSON SCHEMACreateFunctionUrlConfigRequest
JSON SCHEMADestinationConfig
JSON SCHEMAErrorResponse
JSON SCHEMAEventSourceMappingConfiguration
JSON SCHEMAFilterCriteria
JSON SCHEMAFunctionCode
JSON SCHEMAFunctionConfiguration
JSON SCHEMAAWS Lambda Function
JSON SCHEMAFunctionUrlConfig
JSON SCHEMAGetFunctionResponse
JSON SCHEMAGetLayerVersionResponse
JSON SCHEMALayer
JSON SCHEMALayerVersionSummary
JSON SCHEMAListAliasesResponse
JSON SCHEMAListEventSourceMappingsResponse
JSON SCHEMAListFunctionsResponse
JSON SCHEMAListLayerVersionsResponse
JSON SCHEMAListLayersResponse
JSON SCHEMAListVersionsResponse
JSON SCHEMAProvisionedConcurrencyConfig
JSON SCHEMAPublishLayerVersionRequest
JSON SCHEMAPublishLayerVersionResponse
JSON SCHEMAUpdateAliasRequest
JSON SCHEMAUpdateEventSourceMappingRequest
JSON SCHEMAUpdateFunctionCodeRequest
JSON SCHEMAUpdateFunctionConfigurationRequest
JSON SCHEMAUpdateFunctionUrlConfigRequest
JSON SCHEMAVpcConfigResponse
JSON SCHEMAVpcConfig
JSON SCHEMAScroll within the panel for all 35 ·
JSON Structure 34
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Aws Lambda Alias Configuration Structure
JSON STRUCTUREAws Lambda Alias Routing Configuration Structure
JSON STRUCTUREAws Lambda Cors Structure
JSON STRUCTUREAws Lambda Create Alias Request Structure
JSON STRUCTUREAws Lambda Create Event Source Mapping Request Structure
JSON STRUCTUREAws Lambda Create Function Request Structure
JSON STRUCTUREAws Lambda Create Function Url Config Request Structure
JSON STRUCTUREAws Lambda Destination Config Structure
JSON STRUCTUREAws Lambda Error Response Structure
JSON STRUCTUREAws Lambda Event Source Mapping Configuration Structure
JSON STRUCTUREAws Lambda Filter Criteria Structure
JSON STRUCTUREAws Lambda Function Code Structure
JSON STRUCTUREAws Lambda Function Configuration Structure
JSON STRUCTUREAws Lambda Function Url Config Structure
JSON STRUCTUREAws Lambda Get Function Response Structure
JSON STRUCTUREAws Lambda Get Layer Version Response Structure
JSON STRUCTUREAws Lambda Layer Structure
JSON STRUCTUREAws Lambda Layer Version Summary Structure
JSON STRUCTUREAws Lambda List Aliases Response Structure
JSON STRUCTUREAws Lambda List Event Source Mappings Response Structure
JSON STRUCTUREAws Lambda List Functions Response Structure
JSON STRUCTUREAws Lambda List Layer Versions Response Structure
JSON STRUCTUREAws Lambda List Layers Response Structure
JSON STRUCTUREAws Lambda List Versions Response Structure
JSON STRUCTUREAws Lambda Provisioned Concurrency Config Structure
JSON STRUCTUREAws Lambda Publish Layer Version Request Structure
JSON STRUCTUREAws Lambda Publish Layer Version Response Structure
JSON STRUCTUREAws Lambda Update Alias Request Structure
JSON STRUCTUREAws Lambda Update Event Source Mapping Request Structure
JSON STRUCTUREAws Lambda Update Function Code Request Structure
JSON STRUCTUREAws Lambda Update Function Url Config Request Structure
JSON STRUCTUREAws Lambda Vpc Config Response Structure
JSON STRUCTUREAws Lambda Vpc Config Structure
JSON STRUCTUREScroll within the panel for all 34 ·
Examples 34
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Aws Lambda Cors Example
EXAMPLEAws Lambda Layer Example
EXAMPLEScroll within the panel for all 34 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Real-Time File Processing
Automatically process files uploaded to S3, such as image resizing, video transcoding, or document indexing.
Real-Time Stream Processing
Process real-time streaming data from Kinesis or DynamoDB Streams for analytics, monitoring, or ETL pipelines.
Web Application Backends
Build scalable API backends using Lambda with API Gateway or Function URLs for web and mobile applications.
IoT Backends
Process IoT device data from AWS IoT Core for device management, telemetry analysis, and alerting.
Scheduled Tasks
Run periodic tasks like database cleanup, report generation, or data synchronization using EventBridge rules.
CI/CD Automation
Automate build, test, and deployment workflows by triggering Lambda functions from CodePipeline or GitHub events.
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Amazon S3
Trigger functions on object creation, deletion, or modification events in S3 buckets.
Amazon API Gateway
Create RESTful and WebSocket APIs that invoke Lambda functions as backend handlers.
Amazon DynamoDB
Process DynamoDB Streams events to react to table changes in real time.
Amazon SQS
Poll SQS queues and invoke Lambda functions with batches of messages for asynchronous processing.
Amazon SNS
Subscribe Lambda functions to SNS topics for fan-out event processing patterns.
Amazon Kinesis
Process real-time streaming data from Kinesis Data Streams with configurable batch sizes and parallelization.
Amazon EventBridge
Route events from AWS services, SaaS applications, and custom sources to Lambda functions based on rules.
AWS Step Functions
Orchestrate Lambda functions into complex workflows with branching, error handling, and parallel execution.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for AWS Lambda — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 20
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 20 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aws-lambda · machine-readable index on apis.io