Skip to content

Start building

Integration · Cloud and hosting

AI agents for AWS Lambda

List and inspect AWS Lambda functions, their versions and aliases, and run a function with a JSON event, waiting for its answer or queueing it to run in the background, signed with an AWS access key.

Actions
7
Read
5
Write
2

Actions

What your agents can do in AWS Lambda

7 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 5

Look things up. Nothing changes.

  • List functions

    Lists the account's Lambda functions in the connection's Region, up to 50 a page.

  • Get a function

    Gets one function's settings: Configuration (FunctionName, FunctionArn, Runtime, Handler, Role, MemorySize, Timeout, Environment variables, Layers, State, LastUpdateStatus, Version).

  • List a function's versions

    Lists a function's published versions, each with its Version number, Description, LastModified, Runtime and CodeSha256, up to 50 a page, and NextMarker while more remain.

  • List a function's aliases

    Lists a function's aliases (like live or staging), each with its Name, AliasArn, the FunctionVersion it points to and its Description, and NextMarker while more remain.

  • Get account limits and usage

    Gets the account's Lambda limits and use in this Region.

Write 2

Create, change or send.

  • Run a function

    Runs a function with a JSON event and waits for it to finish (up to its timeout, at most 15 minutes).

  • Queue a function run

    Queues a function to run in the background with a JSON event and returns at once (202) without its result.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

Sign-in details

Enter the sign-in details AWS Lambda gives you for its API.

What you enter

  • Access key ID
  • Secret access key

Settings

  • Region

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your AWS Lambda data

    Ask a question in plain words. The agent can list functions, get a function or list a function's versions in AWS Lambda, then answers with what it found.

  • 02

    Let an agent update AWS Lambda

    Have the agent run a function in AWS Lambda as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent AWS Lambda and Slack: it can list functions in AWS Lambda and post a summary to a Slack channel in the same run.

FAQ

AWS Lambda and MyDeepAgents

Can MyDeepAgents connect to AWS Lambda?

Yes. The AWS Lambda connector has 7 actions: 5 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect AWS Lambda?

Enter the sign-in details AWS Lambda gives you for its API. You'll need: Access key ID and Secret access key. The connection also asks for: Region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in AWS Lambda without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use AWS Lambda in workflows as well as agents?

Yes. Every AWS Lambda action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put AWS Lambda to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.