Lambda

Use the Lambda integration to let a workbench call one of your AWS Lambda functions as an action. You describe what the function does and the input it accepts, and the workbench agent decides when to call it, builds the input, and reads the function's response. Typical uses include running a runbook step, querying an internal system, or opening a ticket through code you already maintain.

The Lambda tool reuses a Plural cloud connection for AWS credentials. This guide uses the Plural Console UI. For the complete list of integrations and general tool behavior, see Workbench tools.

Prerequisites

Before you begin, make sure you have:

• A deployed AWS Lambda function and its ARN, such as arn:aws:lambda:us-east-1:123456789012:function:restart-service.
• An AWS cloud connection whose Region is the function's region and whose identity can invoke the function. See Grant invoke access.
• Permission in Plural Console to create a configured tool and edit the target workbench.
• An existing workbench, or permission to create one. See Setting up a workbench.

Grant invoke access

The Lambda tool uses the credentials of the AWS cloud connection: its access keys or Plural's ambient AWS identity, and its Assume role ARN when set. That identity needs lambda:InvokeFunction on the function. The ReadOnlyAccess policy commonly used for cloud queries does not include it.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-east-1:123456789012:function:restart-service*"
    }
  ]
}

If no suitable connection exists, an admin can create one under Settings → Cloud Connections. See Create a cloud connection. Create the connection before you start the Lambda tool form, because the form's create link returns you to the Cloud tool form instead.

Capabilities