Invoke Lambda function action - Amazon Simple Email Service

Invoke Lambda function action

The Lambda action calls your code through a Lambda function and, optionally, notifies you through Amazon SNS. This action has the following options and requirements.

Options

  • Lambda function—The ARN of the Lambda function. An example of a Lambda function ARN is arn:aws:lambda:us-east-1:account-id:function:MyFunction.

  • Invocation type—The invocation type of the Lambda function. An invocation type of RequestResponse means that the execution of the function results in an immediate response. An invocation type of Event means that the function is invoked asynchronously. We recommend that you use Event invocation type unless synchronous execution is required for your use case.

    There is a 30-second timeout on RequestResponse invocations.

    For more information, see Invoking Lambda functions in the AWS Lambda Developer Guide.

  • SNS topic—The name or ARN of the Amazon SNS topic to notify when the specified Lambda function is triggered. An example of an Amazon SNS topic ARN is arn:aws:sns:us-east-1:123456789012:MyTopic. For more information, see Creating an Amazon SNS topic in the Amazon Simple Notification Service Developer Guide.

Requirements

  • The Lambda function that you choose must be in the same AWS Region as the Amazon SES endpoint that you use to receive email.

  • The Amazon SNS topic that you choose must be in the same AWS Region as the Amazon SES endpoint that you use to receive email.

Writing your Lambda function

To process your email, your Lambda function can be invoked asynchronously (that is, using the Event invocation type). The event object passed to your Lambda function will contain metadata pertaining to the inbound email event. You can also use the metadata to access the message content from your Amazon S3 bucket.

If you want to actually control the mail flow, your Lambda function must be invoked synchronously (that is, using the RequestResponse invocation type) and your Lambda function must call the callback method with two arguments: the first argument is null, and the second argument is a disposition property that is set to either STOP_RULE, STOP_RULE_SET, or CONTINUE. If the second argument is null or does not have a valid disposition property, the mail flow continues and further actions and rules are processed, which is the same as with CONTINUE.

For example, you can stop the receipt rule set by writing the following line at the end of your Lambda function code:

callback( null, { "disposition" : "STOP_RULE_SET" });

For AWS Lambda code samples, see Lambda function examples. For examples of high-level use cases, see Use case examples.

Input format

Amazon SES passes information to the Lambda function in JSON format. The top-level object contains a Records array, which is populated with properties eventSource, eventVersion, and ses. The ses object contains receipt and mail objects, which are in exactly the same format as in the Amazon SNS notifications described in Notification contents.

The data that Amazon SES passes to Lambda includes metadata about the message, as well as several email headers. However, it doesn't contain the body of the message.

The following is a high-level view of the structure of the input that Amazon SES provides to the Lambda function.

{ "Records": [ { "eventSource": "aws:ses", "eventVersion": "1.0", "ses": { "receipt": { <same contents as SNS notification> }, "mail": { <same contents as SNS notification> } } } ] }

Return values

Your Lambda function can control mail flow by returning one of the following values:

  • STOP_RULE—No further actions in the current receipt rule will be processed, but further receipt rules can be processed.

  • STOP_RULE_SET—No further actions or receipt rules will be processed.

  • CONTINUE or any other invalid value—This means that further actions and receipt rules can be processed.

The following topics cover samples of incoming mail events, examples of high-level use cases, and AWS Lambda code examples: