Simple lambda function to forward emails from Route 53 domains to another recipient, which can be your personal email address.
Follow instructions as described here: https://aws.amazon.com/blogs/messaging-and-targeting/forward-incoming-email-to-an-external-destination/
Then use lambda_function.py for the lambda function code and email-forwarder-policy.json for the IAM policy.
Differences with this function being:
- adds sender, receiver and message body into the forwarded email
- deletes message s3 object once it's been sent
- uses python 3.9
Run:
make init && make deploy-tf-state-backend
# Edit terraform backend to include the newly created state backend
make migrate-tf-state
make deploy
In order to deploy the example, you need to run the following command:
$ serverless deploy
After running deploy, you should see output similar to:
Deploying aws-python-project to stage dev (us-east-1)
✔ Service deployed to stack aws-python-project-dev (112s)
functions:
hello: aws-python-project-dev-hello (1.5 kB)
After successful deployment, you can invoke the deployed function by using the following command:
serverless invoke --function hello
Which should result in response similar to the following:
{
"statusCode": 200,
"body": "{\"message\": \"Go Serverless v3.0! Your function executed successfully!\", \"input\": {}}"
}
You can invoke your function locally by using the following command:
serverless invoke local --function hello
Which should result in response similar to the following:
{
"statusCode": 200,
"body": "{\"message\": \"Go Serverless v3.0! Your function executed successfully!\", \"input\": {}}"
}
In case you would like to include third-party dependencies, you will need to use a plugin called serverless-python-requirements
. You can set it up by running the following command:
serverless plugin install -n serverless-python-requirements
Running the above will automatically add serverless-python-requirements
to plugins
section in your serverless.yml
file and add it as a devDependency
to package.json
file. The package.json
file will be automatically created if it doesn't exist beforehand. Now you will be able to add your dependencies to requirements.txt
file (Pipfile
and pyproject.toml
is also supported but requires additional configuration) and they will be automatically injected to Lambda package during build process. For more details about the plugin's configuration, please refer to official documentation.