aws-lambda-ses-forwarder | Serverless email forwarding using AWS Lambda and SES | AWS library

Modify the values in the config object at the top of index.js to specify the S3 bucket and object prefix for locating emails stored by SES. Also provide the email forwarding mapping from original destinations to new destination. In AWS Lambda, add a new function and skip selecting a blueprint. Name the function "SesForwarder" and optionally give it a description. Ensure Runtime is set to Node.js 12.x. (Node.js 10.x is also supported.). For the Lambda function code, either copy and paste the contents of index.js into the inline code editor or zip the contents of the repository and upload them directly or via S3. Ensure Handler is set to index.handler.
Modify the values in the config object at the top of index.js to specify the S3 bucket and object prefix for locating emails stored by SES. Also provide the email forwarding mapping from original destinations to new destination.
In AWS Lambda, add a new function and skip selecting a blueprint.
Name the function "SesForwarder" and optionally give it a description. Ensure Runtime is set to Node.js 12.x. (Node.js 10.x is also supported.)
For the Lambda function code, either copy and paste the contents of index.js into the inline code editor or zip the contents of the repository and upload them directly or via S3.
Ensure Handler is set to index.handler.
For Role, choose "Basic Execution Role" under Create New Role. In the popup, give the role a name (e.g., LambdaSesForwarder). Configure the role policy to the following:
Configure the Memory and Timeout settings according to your use case. For simple text emails, a memory limit of 128 MB and timeout of 10 seconds should be sufficient. For emails with large attachments, a memory limit of 512 MB or more and timeout of 30 seconds may be required.
In AWS SES, verify the domains for which you want to receive and forward email. Also configure the DNS MX record for these domains to point to the email receiving (or inbound) SES endpoint. See SES documentation for the email receiving endpoints in each region.
If you have the sandbox level of access to SES, then also verify any email addresses to which you want to forward email that are not on verified domains.
If you have not configured inbound email handling, create a new Rule Set. Otherwise, you can use an existing one.
Create a rule for handling email forwarding functionality.
On the Recipients configuration page, add any email addresses from which you want to forward email.
On the Actions configuration page, add an S3 action first and then an Lambda action.
For the S3 action: Create or choose an existing S3 bucket. Optionally, add an object key prefix. Leave Encrypt Message unchecked and SNS Topic set to [none].
For the Lambda action: Choose the SesForwarder Lambda function. Leave Invocation Type set to Event and SNS Topic set to [none].
Finish by naming the rule, ensuring it's enabled and that spam and virus checking are used.
If you get an error like "Could not write to bucket", follow step 7 before completing this one
If you are asked by SES to add permissions to access lambda:InvokeFunction, agree to it.
The S3 bucket policy needs to be configured so that your IAM user has read and write access to the S3 bucket. When you set up the S3 action in SES, it may add a bucket policy statement that denies all users other than root access to get objects. This causes access issues from the Lambda script, so you will likely need to adjust the bucket policy statement with one like this:
Optionally set the S3 lifecycle for this bucket to delete/expire objects after a few days to clean up the saved emails.