Make your AI agents durable on AWS Lambda
When an agent step fails halfway through, the whole run is usually lost. Pydantic AI now supports AWS Lambda durable functions, so every tool call and task becomes a durable operation that survives failures and resumes where it stopped.
Make a Pydantic AI agent survive failures and resume where it stopped, live on AWS Lambda.
Overview
- Live workshop
- Online event
- Free
Speakers
About this event
AI agents plan their own workflows, call tools and chain tasks together. When a step fails halfway, because of a timeout, a crashed process or a flaky API, the whole run is usually lost. For agents in production, that isn't good enough.
Pydantic AI now supports AWS Lambda durable functions as a durability provider. Every tool call and task your agent runs becomes a durable operation that can survive failures and resume where it stopped. You don't have to rewrite your agent or build your own orchestration.
In this live session, Douwe Maan, lead developer of Pydantic AI, and Thomas Gaigher from AWS, who helped build the integration, take a Pydantic AI agent and make it durable on AWS Lambda. They'll cover where Lambda durable functions fits alongside other durability providers, then get into retries, long-running tasks and observability, with live Q&A from both teams.
Who it's for: Developers and engineers building reliable AI agents in production, whether you already use AWS or are evaluating serverless options.
What you'll learn
- Why agent workflows aren't durable by default, and what that costs you in production
- How durable execution works in Pydantic AI, and where Lambda durable functions fits alongside other providers
- Best practices for running durable agents on Lambda, including retries, long-running tasks and observability
Save your spot
Register today and we'll send you the link to join, reminders, and the recording afterwards.
You're on the list
Check your inbox for joining details and reminders before the session starts.
We couldn't save your registration
Please go back and try again in a moment.
Explore Logfire
Explore our open source packages
