cloudposse / terraform-aws-ses-lambda-forwarder

This is a terraform module that creates an email forwarder using a combination of AWS SES and Lambda running the aws-lambda-ses-forwarder NPM module.

terraform-aws-ses-lambda-forwarder

This is a terraform module that creates an email forwarder using a combination of AWS SES and Lambda running the aws-lambda-ses-forwarder NPM module.

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Introduction

This module provisions a NodeJS script as a AWS Lambda function that uses the inbound/outbound capabilities of AWS Simple Email Service (SES) to run a "serverless" email forwarding service.

Use this module instead of setting up an email server on a dedicated EC2 instance to handle email redirects. It uses AWS SES to receive email and then trigger a Lambda function to process it and forward it on to the chosen destination. This script will allow forwarding emails from any sender to verified destination emails (e.g. opt-in).

Limitations

The SES service only allows sending email from verified addresses or domains. As such, it's mostly suitable for transactional emails (e.g. alerts or notifications). The incoming messages are modified to allow forwarding through SES and reflect the original sender. This script adds a Reply-To header with the original sender's email address, but the From header is changed to display the SES email address.

For example, an email sent by John Doe <[email protected]> to [email protected] will be transformed to:

From: John Doe at [email protected] <[email protected]>
Reply-To: [email protected]

To override this behavior, set a verified fromEmail address (e.g., [email protected]) in the config object and the header will look like this.

From: John Doe <[email protected]>
Reply-To: [email protected]

NOTE: SES only allows receiving email sent to addresses within verified domains. For more information, see: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domains.html

Initially SES users are in a sandbox environment that has a number of limitations. See:
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/limits.html




## Usage


For a complete example, see [examples/complete](examples/complete).

For automated tests of the complete example using [bats](https://github.com/bats-core/bats-core) and [Terratest](https://github.com/gruntwork-io/terratest) (which tests and deploys the example on AWS), see [test](test).

```hcl
variable "relay_email" {
  default     = "[email protected]"
  description = "Email that used to relay from"
}

variable "forward_emails" {
  type = map(list(string))

  default = {
    "[email protected]"  = ["[email protected]"]
    "[email protected]" = ["[email protected]"]
  }

  description = "Emails forward map"
}

module "ses_lambda_forwarder" {
  source = "cloudposse/ses-lambda-forwarder/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  namespace  = var.namespace
  stage      = var.stage
  name       = var.name
  delimiter  = var.delimiter
  attributes = var.attributes
  tags       = var.tags

  region = var.region
  domain = var.domain

  relay_email    = var.relay_email
  forward_emails = var.forward_emails
}

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Requirements

Name	Version
terraform	>= 0.13.0
aws	>= 2.0
external	>= 1.2
local	>= 1.3
template	>= 2.2

Providers

Name	Version
aws	>= 2.0

Modules

Name	Source	Version
artifact	cloudposse/module-artifact/external	0.7.1
this	cloudposse/label/null	0.25.0

Resources

Name	Type
aws_iam_policy.lambda	resource
aws_iam_role.lambda	resource
aws_iam_role_policy_attachment.lambda	resource
aws_lambda_alias.default	resource
aws_lambda_function.default	resource
aws_lambda_permission.ses	resource
aws_route53_record.default	resource
aws_route53_record.mx	resource
aws_route53_record.txt	resource
aws_s3_bucket.default	resource
aws_s3_bucket_policy.default	resource
aws_ses_active_receipt_rule_set.default	resource
aws_ses_domain_identity.default	resource
aws_ses_domain_identity_verification.default	resource
aws_ses_receipt_rule.default	resource
aws_ses_receipt_rule_set.default	resource
aws_caller_identity.current	data source
aws_iam_policy_document.assume	data source
aws_iam_policy_document.lambda	data source
aws_iam_policy_document.s3	data source
aws_route53_zone.default	data source

Inputs

Name	Description	Type	Default	Required
access_log_bucket_name	Name of the S3 bucket where s3 access log will be sent to	string	""	no
additional_tag_map	Additional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id. This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration.	map(string)	{}	no
artifact_filename	Artifact filename	string	"lambda.zip"	no
artifact_url	URL template for the remote artifact	string	"https://artifacts.cloudposse.com/$${module_name}/$${git_ref}/$${filename}"	no
attributes	ID element. Additional attributes (e.g. workers or cluster) to add to id, in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the delimiter and treated as a single ID element.	list(string)	[]	no
context	Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as null to use default value. Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged.	any	{ "additional_tag_map": {}, "attributes": [], "delimiter": null, "descriptor_formats": {}, "enabled": true, "environment": null, "id_length_limit": null, "label_key_case": null, "label_order": [], "label_value_case": null, "labels_as_tags": [ "unset" ], "name": null, "namespace": null, "regex_replace_chars": null, "stage": null, "tags": {}, "tenant": null }	no
delimiter	Delimiter to be used between ID elements. Defaults to - (hyphen). Set to "" to use no delimiter at all.	string	null	no
descriptor_formats	Describe additional descriptors to be output in the descriptors output map. Map of maps. Keys are names of descriptors. Values are maps of the form {<br> format = string<br> labels = list(string)<br>} (Type is any so the map values can later be enhanced to provide additional options.) format is a Terraform format string to be passed to the format() function. labels is a list of labels, in order, to pass to format() function. Label values will be normalized before being passed to format() so they will be identical to how they appear in id. Default is {} (descriptors output will be empty).	any	{}	no
domain	Root domain name	string	n/a	yes
enabled	Set to false to prevent the module from creating any resources	bool	null	no
environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	string	null	no
forward_emails	Map of forward emails	map(list(string))	{ "[email protected]": [ "[email protected]" ] }	no
id_length_limit	Limit id to this many characters (minimum 6). Set to 0 for unlimited length. Set to null for keep the existing setting, which defaults to 0. Does not affect id_full.	number	null	no
label_key_case	Controls the letter case of the tags keys (label names) for tags generated by this module. Does not affect keys of tags passed in via the tags input. Possible values: lower, title, upper. Default value: title.	string	null	no
label_order	The order in which the labels (ID elements) appear in the id. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	list(string)	null	no
label_value_case	Controls the letter case of ID elements (labels) as included in id, set as tag values, and output by this module individually. Does not affect values of tags passed in via the tags input. Possible values: lower, title, upper and none (no transformation). Set this to title and set delimiter to "" to yield Pascal Case IDs. Default value: lower.	string	null	no
labels_as_tags	Set of labels (ID elements) to include as tags in the tags output. Default is to include all labels. Tags with empty values will not be included in the tags output. Set to [] to suppress all generated tags. Notes: The value of the name tag, if included, will be the id, not the name. Unlike other null-label inputs, the initial setting of labels_as_tags cannot be changed in later chained modules. Attempts to change it will be silently ignored.	set(string)	[ "default" ]	no
lambda_runtime	Lambda runtime	string	"nodejs12.x"	no
name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a tag. The "name" tag is set to the full id string. There is no tag with the value of the name input.	string	null	no
namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	string	null	no
regex_replace_chars	Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.	string	null	no
region	AWS Region the SES should reside in	string	n/a	yes
relay_email	Email that used to relay from	string	n/a	yes
s3_bucket_encryption_enabled	When set to 'true' the 'aws_s3_bucket' resource will have AES256 encryption enabled by default	bool	true	no
spf	DNS SPF record value	string	"v=spf1 include:amazonses.com -all"	no
stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	string	null	no
tags	Additional tags (e.g. {'BusinessUnit': 'XYZ'}). Neither the tag keys nor the tag values will be modified by this module.	map(string)	{}	no
tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	string	null	no
tracing_config_mode	Can be either PassThrough or Active. If PassThrough, Lambda will only trace the request from an upstream service if it contains a tracing header with 'sampled=1'. If Active, Lambda will respect any tracing header it receives from an upstream service.	string	"PassThrough"	no
versioning_enabled	A state of versioning. Versioning is a means of keeping multiple variants of an object in the same bucket	bool	true	no

Outputs

Name	Description
artifact_base64sha256	Base64 encoded SHA256 hash of the artifact file
artifact_file	Full path to the locally downloaded artifact
artifact_git_ref	Git commit hash corresponding to the artifact
artifact_url	URL corresponding to the artifact
lambda_function_arn	Lamnda Function ARN
lambda_function_source_code_size	The size in bytes of the Lambda Function .zip file
lambda_function_version	Latest published version of the Lambda Function
lambda_iam_policy_arn	Lamnda IAM Policy ARN
lambda_iam_policy_id	Lamnda IAM Policy ID
lambda_iam_policy_name	Lamnda IAM Policy name
s3_bucket_arn	Lamnda IAM Policy ARN
s3_bucket_domain_name	Lamnda IAM Policy ARN
s3_bucket_id	Lamnda IAM Policy name
ses_domain_identity_arn	The ARN of the domain identity
ses_domain_identity_verification_arn	The ARN of the domain identity
ses_receipt_rule_name	The name of the SES receipt rule
ses_receipt_rule_set_name	The name of the SES receipt rule set

References

For additional context, refer to some of these links.

• aws-lambda-ses-forwarder - A Node.js script for AWS Lambda that uses the inbound/outbound capabilities of AWS Simple Email Service (SES) to run a "serverless" email forwarding service.

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it with you.
✅ You own everything.
✅ Your team wins.

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

• Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
• Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
• Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
• Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
• GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Day-2: Your Operational Mastery

• Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
• Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
• Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
• Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
• Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
• Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
• Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

1. Review our Code of Conduct and Contributor Guidelines.
2. Fork the repo on GitHub
3. Clone the project to your own machine
4. Commit changes to your own branch
5. Push your work back up to your fork
6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Complete license is available in the LICENSE file.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

---

Copyright © 2017-2024 Cloud Posse, LLC

terraform-aws-ses-lambda-forwarder's Issues

Project dead?

@osterman @goruha

Is this project still being maintained? It's been several months since Terraform 0.12.x release and this hasn't been updated yet. Any ETA? Looks like there is an existing PR for it

Add Example Usage

what

• Add example invocation

why

• We need this so we can soon enable automated continuous integration testing of module

Refactor Zip Creation as Part of CI/CD

what

Suggested improvements: (can be implemented in separate PR)

• Build/package zip as part of CI to create an artifact
• Attach ZIP artifact to release
• Derive module version from git
• rename module to terraform-aws-ses-lambda-forwarder
• ensure S3 bucket uses encryption at rest (use https://github.com/cloudposse/terraform-aws-s3-log-storage for bucket creation)

why

• Artifacts should be built from CI/CD and not by developers
• Artifacts should not be committed to source control

tips

this appears to work to introspect the version of the current module:

variable "git_ref_type" {
  default = "tag"
}

data "external" "example" {
  count = "${var.git_ref_type == "tag" || var.git_ref_type == "branch" ? 1 : 0}"
  program = ["git", "-C", "${path.module}", "${var.git_ref_type}", "--points-at", "HEAD", "--format={\"ref\": \"%(refname:lstrip=2)\"}"]
}


output "ref" {
  value = "${join("", data.external.example.*.result.ref)}"
}

outputs:
ref = test-0.1.1

It fails if git_ref is not type "tag" or "branch"

404 error when loading lambda.zip

When running the example hcl from the readme I'm getting the following error:

Error: failed to execute "curl": curl: (22) The requested URL returned error: 404
on .terraform/modules/ses_lambda_forwarder.artifact/main.tf line 1, in data "external" "curl":
1: data "external" "curl" {

It looks like there's a problem with the artifact url here:

terraform-aws-ses-lambda-forwarder/lambda.tf

Line 73 in f6f9346

url = var.artifact_url

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Dependencies missing from lambda package

Found a bug? Maybe our Slack Community can help.

Describe the Bug

Artifacts do not contain node_modules, thus lambda fails to execute with ImportError

Expected Behavior

Lambda functions properly and contains vendored dependencies.

Steps to Reproduce

Check the logs, notice that there are no node_modules being uploaded

https://github.com/cloudposse/terraform-aws-ses-lambda-forwarder/runs/823734871?check_suite_focus=true

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Base branch does not exist - skipping

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update terraform cloudposse/module-artifact/external to v0.8.0 (main)

Detected dependencies

terraform

lambda.tf

• cloudposse/module-artifact/external 0.7.1

versions.tf

• aws >= 2.0
• external >= 1.2
• local >= 1.3
• template >= 2.2
• hashicorp/terraform >= 0.13.0

---

• Check this box to trigger a request for Renovate to run again on this repository

Current aws_route53_zone data resource does not allow comment attr

The current provider version does not support comment as an attribute to the aws_route53_zone data resource. https://www.terraform.io/docs/providers/aws/d/route53_zone.html

Some solutions:

1. Remove the comment attr from the resource. This will always cause an error if there is a hosted zone with the same name in the same account.
2. Replace domain_name with hosted_zone_id
3. Lock provider version to when the provider supported it

Happy to make PR

Add README

what

• Add a README.yaml

aws_ses_receipt_rule.default: expected s3_action.0.position to be at least (1), got 0

Hi,
I have use this project for learning aws and terraform. I have created a terraform.tfvars file and when I run terraform apply, I get the message

aws_ses_receipt_rule.default: expected s3_action.0.position to be at least (1), got 0

When I change ses.tf to read position = 1 instead of position = 0, I can apply. Is this a problem in the ses.tf file or is it my usage of it that is wrong?

Support external domains

Describe the Feature

Currently, this module tries to configure route53. It would be nice if I could use it with domains that are not controlled by AWS.

Expected Behavior

A clear and concise description of what you expected to happen.

Use Case

Domain is already configured outside of AWS. Leaving domain out of the config is not possible:

Error: Missing required argument

  on main.tf line 20, in module "ses_lambda_forwarder":
  20: module "ses_lambda_forwarder" {

The argument "domain" is required, but no definition was found.

Describe Ideal Solution

A clear and concise description of what you want to happen. If you don't know, that's okay.

Alternatives Considered

n/a