AI SRE Agent Debugs a Lambda Timeout with the AWS MCP Server: AURA

A scheduled Lambda quietly stops completing and nothing pages you. AURA finds the function, reads its logs, and comes back with a three-second timeout.

Learn more about AURA → https://www.mezmo.com/aura
Get started today → https://github.com/mezmo/aura
Get deployment help → https://www.mezmo.com/contact

The usual path is opening the console, tracking down the right log group, and reading CloudWatch by hand. Here AURA connects to AWS through the MCP proxy AWS publishes, run locally with uvx against an AWS CLI that is already configured, so there are no new credentials to issue.

From there it makes the connections itself: it recognizes the function as a Lambda, finds the CloudWatch logs available to it, and queries them. It names the timeout as the cause and verifies that against the log output, then hands back recommended remediation steps rather than applying them. It also checks whether a service-wide Lambda outage would explain the failure, and confirms that it would not.

AURA is built for SREs and cloud engineers who need a cause for a failing serverless function without leaving the terminal.

For more detail, visit
https://www.mezmo.com/videos/ai-sre-agent-debugs-a-lambda-timeout-via-aws-mcp-server

Chapters

0:00 Debugging a scheduled Lambda that stopped completing

0:12 Connecting through AWS's MCP proxy and the AWS CLI

0:33 Adding the proxy as an MCP server with uvx

1:02 Starting AURA and handing it the function

1:30 AURA finds the Lambda and queries its CloudWatch logs

2:09 A three-second timeout, verified in the logs

2:30 Ruling out a service-wide Lambda outage and recommending fixes

#AWSLambda #AISREAgent #Serverless