Lambda / Client / invoke



Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or asynchronously. By default, Lambda invokes your function synchronously (i.e. the InvocationType is RequestResponse). To invoke a function asynchronously, set InvocationType to Event. Lambda passes the ClientContext object to your function for synchronous invocations only.

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.

When an error occurs, your function may be invoked multiple times. Retry behavior varies by error type, client, event source, and invocation type. For example, if you invoke a function asynchronously and it returns an error, Lambda executes the function up to two more times. For more information, see Error handling and automatic retries in Lambda.

For asynchronous invocation, Lambda adds events to a queue before sending them to your function. If your function does not have enough capacity to keep up with the queue, events may be lost. Occasionally, your function may receive the same event multiple times, even if no error occurs. To retain events that were not processed, 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, quota errors, or issues with your function’s code and configuration. For example, Lambda returns TooManyRequestsException if running 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 disconnect 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. For details on how to set up permissions for cross-account invocations, see Granting function access to other accounts.

See also: AWS API Documentation

Request Syntax

response = client.invoke(
  • FunctionName (string) –


    The name or ARN of the Lambda function, version, or alias.

    Name formats

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

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

    • Partial ARN123456789012: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 (string) –

    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 one is 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 (string) – Set to Tail to include the execution log in the response. Applies to synchronously invoked functions only.

  • ClientContext (string) – Up to 3,583 bytes of base64-encoded data about the invoking client to pass to the function in the context object. Lambda passes the ClientContext object to your function for synchronous invocations only.

  • Payload (bytes or seekable file-like object) –

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

    You can enter the JSON directly. For example, --payload '{ "key": "value" }'. You can also specify a file path. For example, --payload file://payload.json.

  • Qualifier (string) – Specify a version or alias to invoke a published version of the function.

Return type:



Response Syntax

    'StatusCode': 123,
    'FunctionError': 'string',
    'LogResult': 'string',
    'Payload': StreamingBody(),
    'ExecutedVersion': 'string'

Response Structure

  • (dict) –

    • StatusCode (integer) –

      The HTTP status code is in the 200 range for a successful request. For the RequestResponse invocation type, this status code is 200. For the Event invocation type, this status code is 202. For the DryRun invocation type, the status code is 204.

    • FunctionError (string) –

      If present, indicates that an error occurred during function execution. Details about the error are included in the response payload.

    • LogResult (string) –

      The last 4 KB of the execution log, which is base64-encoded.

    • Payload (StreamingBody) –

      The response from the function, or an error object.

    • ExecutedVersion (string) –

      The version of the function that executed. When you invoke a function with an alias, this indicates which version the alias resolved to.


  • Lambda.Client.exceptions.ServiceException

  • Lambda.Client.exceptions.ResourceNotFoundException

  • Lambda.Client.exceptions.InvalidRequestContentException

  • Lambda.Client.exceptions.RequestTooLargeException

  • Lambda.Client.exceptions.UnsupportedMediaTypeException

  • Lambda.Client.exceptions.TooManyRequestsException

  • Lambda.Client.exceptions.InvalidParameterValueException

  • Lambda.Client.exceptions.EC2UnexpectedException

  • Lambda.Client.exceptions.SubnetIPAddressLimitReachedException

  • Lambda.Client.exceptions.ENILimitReachedException

  • Lambda.Client.exceptions.EFSMountConnectivityException

  • Lambda.Client.exceptions.EFSMountFailureException

  • Lambda.Client.exceptions.EFSMountTimeoutException

  • Lambda.Client.exceptions.EFSIOException

  • Lambda.Client.exceptions.SnapStartException

  • Lambda.Client.exceptions.SnapStartTimeoutException

  • Lambda.Client.exceptions.SnapStartNotReadyException

  • Lambda.Client.exceptions.EC2ThrottledException

  • Lambda.Client.exceptions.EC2AccessDeniedException

  • Lambda.Client.exceptions.InvalidSubnetIDException

  • Lambda.Client.exceptions.InvalidSecurityGroupIDException

  • Lambda.Client.exceptions.InvalidZipFileException

  • Lambda.Client.exceptions.KMSDisabledException

  • Lambda.Client.exceptions.KMSInvalidStateException

  • Lambda.Client.exceptions.KMSAccessDeniedException

  • Lambda.Client.exceptions.KMSNotFoundException

  • Lambda.Client.exceptions.InvalidRuntimeException

  • Lambda.Client.exceptions.ResourceConflictException

  • Lambda.Client.exceptions.ResourceNotReadyException

  • Lambda.Client.exceptions.RecursiveInvocationException


The following example invokes version 1 of a function named my-function with an empty event payload.

response = client.invoke(


Expected Output:

    'Payload': '200 SUCCESS',
    'StatusCode': 200,
    'ResponseMetadata': {
        '...': '...',

The following example invokes version 1 of a function named my-function asynchronously.

response = client.invoke(


Expected Output:

    'Payload': '',
    'StatusCode': 202,
    'ResponseMetadata': {
        '...': '...',