Skip to main content
The Lambda connector combines the Lambda API with the function’s CloudWatch logs and metrics, so one call answers “what has this function been doing”. Setup and the IAM policy are on the AWS page.

​
Tools

​
Safety

  • Environment values never leave AWS through Danube. Get Configuration returns variable names only; values are dropped before the answer is built.
  • Invoke really runs the function, with all its side effects, so it is a write tool: refused on a read_only connection and confirmed on every call. Grant lambda:InvokeFunction only on the functions agents may run.
  • Only synchronous (RequestResponse) invocations. A function that is already running is not stopped by the call’s timeout.

​
Example prompts

  • “Pull the last 50 errors from /aws/lambda/checkout in the past hour.”
  • “Is checkout timing out? Show recent invocations, cold starts and p99 duration.”
  • “Which environment variables does billing-webhook expect?”
  • “Invoke report-daily with {\"date\": \"2026-09-25\"} and show me the result.”