AWS Launches Durable Execution Telemetry Exporter and MCP Server to Solve Lambda Observability Gaps

Amazon Web Services (AWS) introduced the Durable Execution Telemetry Exporter on October 28, 2026, an observability plugin designed for AWS Lambda durable functions. These functions can run for minutes, days, or even up to a year, with their execution often spread across many separate Lambda invocations interspersed with waits and retries. Traditional Lambda observability tools are built for single invocations, causing one logical execution to be fragmented across multiple log streams. This makes it difficult to answer critical questions such as "how far did my durable execution get," "which step failed," or "how many times did it retry."

The new Exporter plugin runs inside the Lambda function as part of the SDK, subscribing to the SDK's instrumentation lifecycle. It builds a cumulative snapshot of the entire execution on every invocation, rather than a delta view. This means developers can generate a single JSON record containing all steps, waits, callbacks, timing, retry attempts, status, and errors with just a one-line configuration change. This record can be sent to 13 different destinations, including S3, DynamoDB, and CloudWatch, turning cross-invocation workflow monitoring into standard database queries.

Simultaneously, AWS released a companion Durable Execution Telemetry MCP server. The Model Context Protocol (MCP) is a standard that allows AI models to connect to external tools. This MCP server enables AI coding agents to directly query the telemetry data described above. Developers can ask AI agents questions in natural language, such as "Which step got slower after last week’s deployment?" or "Which customers did last night’s payment failures affect?", and the agent will retrieve answers by querying the structured telemetry records.