In our article about Posting Form Content to a Slack Channel via an AWS Lambda Function, we elaborated on how to take advantage of AWS Lambda to handle a delicate process you don’t want to expose to the public in your single-page application.

In this guide, we’ll provide you with an AWS Lambda function for sending an email to a visitor who submitted a form, leaving their email address for registering, downloading a file, getting access to some service or benefit, or something similar. We’ll use AWS SES (Simple Email Service) for sending out the emails, but you might as well use SendGrid, MailChimp, or what you prefer.

We are assuming that you already have a form and have gathered from the article linked above how to set up an AWS gateway for passing the form fields to a Lambda function that processes them. So let’s concentrate on the core functionality!

The task of the Lambda function is to handle the events coming in via the AWS Gateway associated with it. It receives two arguments, objects named event and context here. event includes the request details, first and foremost the form field values posted on form submission. The context object is for notifying the caller (our form in this case) of the execution result, which can then be reflected on the page. Alternatively, you can have the gateway act on the result, for example, by setting the HTTP status code accordingly.

Here’s the Lambda function; we’re going to explain further details below.

In our case, the request parameters passed to the function are email and name. After setting up and configuring AWS, identifying invalid email addresses, and cleaning up the name, the HTML and plain text versions of the email contents are defined:  htmlBody and textBody.

After these preparatory steps, an email params object is filled with the message details and then handed over to the AWS SES sendEmail function. sendEmail is executed asynchronously, so we are using a Promise to handle the execution result.

Please keep in mind that AWS SES requires you to verify the email address specified as the Source in the params before it can be used as a sender.

As said, the basic functioning of a form, which connects to a remote service, is explained in Posting Form Content to a Slack Channel via an AWS Lambda Function. So we are limiting ourselves to the form submission handler:

This handler simply collects the form field values from the form’s state variables and places them into the payload object, which is then posted via an AJAX request to the given AWS Gateway URL.

Almost. Don’t forget to harden your form and your AWS Gateway against spamming and misuse, for example by not blindly accepting all user input, integrating a captcha service, setting a rate limit and processing only requests originating from your site.