paws.compute (version 0.1.0)

lambda_invoke: Invokes a Lambda function

Description

Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or asynchronously. To invoke a function asynchronously, set InvocationType to Event.

Usage

lambda_invoke(FunctionName, InvocationType, LogType, ClientContext,
  Payload, Qualifier)

Arguments

FunctionName

[required] The name of the Lambda function, version, or alias.

Name formats

• Function name - my-function (name-only), my-function:v1 (with alias).

• Function ARN - arn:aws:lambda:us-west-2:123456789012:function:my-function.

• Partial ARN - 123456789012:function:my-function.

You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.

InvocationType

Choose from the following options.

• RequestResponse (default) - Invoke the function synchronously. Keep the connection open until the function returns a response or times out. The API response includes the function response and additional data.

• Event - Invoke the function asynchronously. Send events that fail multiple times to the function's dead-letter queue (if it's configured). The API response only includes a status code.

• DryRun - Validate parameter values and verify that the user or role has permission to invoke the function.

LogType

Set to Tail to include the execution log in the response.

ClientContext

Up to 3583 bytes of base64-encoded data about the invoking client to pass to the function in the context object.

Payload

The JSON that you want to provide to your Lambda function as input.

Qualifier

Specify a version or alias to invoke a published version of the function.

Request syntax

svc$invoke(
  FunctionName = "string",
  InvocationType = "Event"|"RequestResponse"|"DryRun",
  LogType = "None"|"Tail",
  ClientContext = "string",
  Payload = raw,
  Qualifier = "string"
)

Details

For synchronous invocation, details about the function response, including errors, are included in the response body and headers. For either invocation type, you can find more information in the execution log and trace. To record function errors for asynchronous invocations, configure your function with a dead letter queue.

The status code in the API response doesn't reflect function errors. Error codes are reserved for errors that prevent your function from executing, such as permissions errors, limit errors, or issues with your function's code and configuration. For example, Lambda returns TooManyRequestsException if executing the function would cause you to exceed a concurrency limit at either the account level (ConcurrentInvocationLimitExceeded) or function level (ReservedFunctionConcurrentInvocationLimitExceeded).

For functions with a long timeout, your client might be disconnected during synchronous invocation while it waits for a response. Configure your HTTP client, SDK, firewall, proxy, or operating system to allow for long connections with timeout or keep-alive settings.

This operation requires permission for the lambda:InvokeFunction action.

Examples

# NOT RUN {
# This operation invokes a Lambda function
# }
# NOT RUN {
svc$invoke(
  ClientContext = "MyApp",
  FunctionName = "MyFunction",
  InvocationType = "Event",
  LogType = "Tail",
  Payload = "fileb://file-path/input.json",
  Qualifier = "1"
)
# }
# NOT RUN {
# }