> ## Documentation Index
> Fetch the complete documentation index at: https://trytilde.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Lambda agents

> Run an agent as an AWS Lambda function that the Tilde gateway invokes through the AWS API.

A Lambda agent runs as an AWS Lambda function. The gateway invokes the function through the AWS API, so you need no Function URL or API Gateway. The function then calls back to the gateway for runtime operations and telemetry.

<Info>
  Lambda agents require a deployed [gateway](/docs/deployment/gateway) with AWS credentials.
</Info>

## Where Lambda agents run

A Lambda agent runs in your own AWS account. You wrap your agent with the SDK's Lambda handler and deploy it as a standard Lambda function.

## What a Lambda agent needs

| Requirement | Detail |
| - | - |
| Invoke permission | The gateway's AWS role can invoke the function. |
| A registered deployment | You register the function's ARN as a deployment. A Lambda release can take traffic as soon as it is registered. |
| A private network path | The function reaches the gateway privately, through your VPC, or through VPN or Direct Connect for a gateway outside AWS. |

The gateway can reach the Lambda API through a [Lambda interface VPC endpoint](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc-endpoints.html), so invocations stay off the public internet.

Lambda suits bursty and low-volume agents, where you would rather not run idle containers. Account for cold starts when you size the function.