AWS Lambda connector
The AWS Lambda connector calls the AWS Lambda API to invoke functions, list the functions in a region, and read a function's configuration. Use it to run your own remediation or enrichment code in AWS.
You can use this connector in Agent Builder and Workflows.
You can create connectors in Stack Management > Connectors.
AWS Lambda connectors have the following configuration properties:
- AWS Region
- The AWS Region where your Lambda functions are, for example
us-east-1. All actions run against this single region. To work across multiple regions, create one connector per region.
AWS credentials
- Access Key ID
- The AWS IAM access key ID used to sign every request with Signature Version 4 (SigV4).
- Secret Access Key
- The AWS IAM secret access key paired with the access key ID above.
You can test connectors when you create or edit the connector in Kibana. The test calls the Lambda ListFunctions API to verify that the credentials can authenticate against Lambda in the configured region.
The AWS Lambda connector has the following actions:
invoke- Invoke a function by name or ARN (
functionName), with an optional JSONpayloadand an optional version or alias (qualifier). SetinvocationTypetoRequestResponse(the default) to wait for the result and the end of the execution log,Eventto start the function without waiting, orDryRunto check permissions without running it. listFunctions- List the functions in the configured region with their name, ARN, runtime, handler, memory, timeout, and last-modified date. Use
maxItemsto limit the number of functions returned, and pass thenextMarkerfrom the response asmarkerto get the next page. getFunction- Get the configuration of one function (
functionName, optionalqualifier): ARN, runtime, execution role, handler, timeout, memory, state, and last update status.
Use the Action configuration settings to customize connector networking, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use xpack.actions.customHostSettings to set per-host configurations.
- Sign in to the AWS IAM console.
- Create (or choose) an IAM user dedicated to this connector.
- Attach a policy granting at least the following actions:
lambda:InvokeFunctionandlambda:GetFunction, scoped to the functions you want the connector to uselambda:ListFunctions, which applies to all functions in the account (*)
- Create an access key for that user (Security credentials > Access keys > Create access key).
- Copy the Access key ID and Secret access key, and enter them along with the AWS Region when configuring the connector in Kibana.