AWS Lambda API

Name: AWS Lambda API API
Brand: AWS Lambda API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureServerlessapiKey50 EndpointsREST

For Agents

Create, update, invoke, and configure AWS Lambda functions, manage versions and aliases, attach layers, and wire event source mappings to streams and queues so an agent can deploy and run serverless code on demand.

Quickstart

Get started with AWS Lambda API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"invoke an AWS Lambda function"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS Lambda API API.

Create and update Lambda functions from a zip deployment package or a container image stored in Amazon ECR

Invoke a function synchronously, asynchronously, or with response streaming for long-lived outputs

Manage published versions and weighted aliases for blue/green and canary traffic shifting

Attach Lambda layers to share code, dependencies, or runtimes across multiple functions

GET STARTED

Start building with AWS Lambda API API

Explore with Jentic

View OpenAPI Document

AWS Lambda runs code in response to events without requiring you to provision or manage servers. The Lambda API gives full control over functions, including creating and updating function code from zip archives or container images, configuring memory and timeout, attaching layers, managing aliases and versions, and wiring event source mappings to streams from Kinesis, DynamoDB, SQS, MSK, and self-managed Kafka. It also supports synchronous, asynchronous, and streaming invocation, plus URL-based public endpoints via Lambda function URLs.

Use Cases

Patterns agents use AWS Lambda API API for, with concrete tasks.

★ Event-Driven SQS Processing

Run a Lambda function for every message that lands on an SQS queue without writing a poller. Create the function with createFunction, then create an event source mapping that points at the queue ARN with a configured batch size and reporting on partial batch failures. Lambda scales the function up to the queue's concurrency limit, retries failed messages, and routes poison messages to a dead-letter queue. Setup takes around an hour including IAM permissions.

Create a Lambda function order-processor (Python 3.12, 512 MB, 30s timeout) from a zip in S3, then create an event source mapping pointing at queue arn:aws:sqs:eu-west-1:...:orders with BatchSize=10 and FunctionResponseTypes=ReportBatchItemFailures.

Canary Deploys via Aliases

Roll out a new function version to a small percentage of production traffic and ramp up if metrics stay healthy. Use publishVersion to snapshot the current function, then updateAlias on the production alias with a routing config that sends 10 percent of invokes to the new version. Cut over to 100 percent or roll back by editing the alias. This is the standard pattern for AWS SAM and AWS CodeDeploy traffic shifting.

Call publishVersion on function checkout-api, then updateAlias prod with FunctionVersion set to the previous live version and RoutingConfig.AdditionalVersionWeights set to {newVersion: 0.1}.

Container Image Function for Heavy Dependencies

Package a Lambda function as a container image when the deployment exceeds the 250 MB unzipped zip limit or needs custom runtimes, common for ML inference, headless browsers, or large native libraries. Build and push the image to Amazon ECR, then create a function with PackageType=Image pointing at the ECR URI. Lambda runs the image with up to 10 GB memory and 15-minute timeouts.

Create function pdf-renderer with PackageType=Image, ImageUri=123456789012.dkr.ecr.eu-west-1.amazonaws.com/pdf-renderer:v3, MemorySize=3008, Timeout=120, and Architectures=['arm64'].

Agent-Triggered Serverless Tasks

Let an AI agent execute one-off serverless work, such as reformatting a document, fetching a fresh report, or running a price calculation, by invoking pre-deployed Lambda functions through Jentic. The agent picks the right function from Jentic's intent search, passes structured input, and receives the function response. Long-lived AWS credentials stay in the Jentic vault; the agent only ever calls Jentic with a scoped key.

Search Jentic for 'invoke a lambda function and get the response', load the invoke schema, and execute it with FunctionName=customer-summary, Payload=JSON of {customerId: 'cus_42'}.

Key Endpoints

50 endpoints — aws lambda runs code in response to events without requiring you to provision or manage servers.

METHOD

PATH

DESCRIPTION

POST

/2015-03-31/functions

Create a Lambda function

GET

/2015-03-31/functions

List functions in this region

GET

/2015-03-31/functions/{FunctionName}

Get a function and its configuration

PUT

/2015-03-31/functions/{FunctionName}/code

Update function code

PUT

/2015-03-31/functions/{FunctionName}/configuration

Update function memory, timeout, env, and other config

POST

/2015-03-31/functions/{FunctionName}/invocations

Invoke a function synchronously or asynchronously

POST

/2015-03-31/functions/{FunctionName}/invoke-with-response-stream

Invoke a function and stream the response

POST

/2015-03-31/functions/{FunctionName}/aliases

Create an alias for traffic routing

POST

/2015-03-31/functions

Create a Lambda function

GET

/2015-03-31/functions

List functions in this region

GET

/2015-03-31/functions/{FunctionName}

Get a function and its configuration

PUT

/2015-03-31/functions/{FunctionName}/code

Update function code

PUT

/2015-03-31/functions/{FunctionName}/configuration

Update function memory, timeout, env, and other config

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access key ID and secret access key for AWS Lambda API are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing credentials and the raw IAM secrets never enter the agent context. Jentic computes the AWS Signature Version 4 signature server-side for every request.

Intent-based discovery

Agents search Jentic by intent (for example, 'invoke a Lambda function') and Jentic returns matching AWS Lambda API operations with their input schemas, the correct AWS service endpoint, and the required IAM action, so the agent can invoke the right call without crawling the AWS docs.

Time to first call

Direct AWS Lambda API integration: 1-3 days for AWS SDK setup, IAM role configuration, Sigv4 signing, and error handling. Through Jentic: under 1 hour, search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon EC2

Long-running VMs for workloads that need persistent state, custom networking, or runtimes Lambda does not support.

Choose EC2 when the workload exceeds Lambda's 15-minute timeout, requires GPU access patterns Lambda does not offer, or needs persistent local disk; choose Lambda for short, event-driven tasks.

Complementary

Amazon API Gateway

Fronts Lambda functions with REST or HTTP APIs, custom domains, throttling, and request validation.

Use API Gateway when you need an HTTP entry point with authorisation, mapping templates, or custom domains; use Lambda function URLs for the simplest direct HTTPS endpoint.

Complementary

Amazon CloudWatch

Captures Lambda function logs, metrics, and alarms for observability of running functions.

Use CloudWatch when the agent needs to inspect function logs or set alarms on errors and duration; use Lambda for the function lifecycle itself.

FAQs

Specific to using AWS Lambda API API through Jentic.

What authentication does the AWS Lambda API use?

All requests are signed with AWS Signature Version 4 using an AWS access key ID and secret access key. Through Jentic, the keys live encrypted in the Jentic vault and signing is performed server-side; the agent only sees a scoped Jentic credential reference.

Can I deploy a Lambda function from a container image with this API?

Yes. Call createFunction with PackageType=Image and an ImageUri pointing at an Amazon ECR repository in the same region. Container image functions support up to 10 GB memory, 15-minute timeouts, and arm64 or x86_64 architectures.

What are the rate limits for the AWS Lambda API?

Lambda enforces account-level concurrent execution limits (default 1,000) and per-function reserved or provisioned concurrency that you set explicitly. The control-plane API operations (createFunction, updateFunctionCode, etc.) are subject to standard AWS request throttling and return ThrottlingException with retry guidance.

How do I invoke a Lambda function and get the response through Jentic?

Search Jentic for 'invoke a Lambda function' and execute the returned operation with FunctionName and a JSON Payload. The operation maps to POST /2015-03-31/functions/{FunctionName}/invocations and returns the function's payload synchronously when InvocationType is RequestResponse.

Does the API support streaming responses?

Yes. Use POST /2015-03-31/functions/{FunctionName}/invoke-with-response-stream to receive a chunked response from a function configured with response streaming. This is suitable for LLM-style outputs and large file generation that should not buffer in memory.

Is AWS Lambda free to use?

Lambda has an always-free tier of 1 million requests and 400,000 GB-seconds of compute per month. Beyond that, you pay per request and per GB-second of memory consumed at the duration billed in 1 ms increments.