Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 2.67 KB

README.md

File metadata and controls

31 lines (21 loc) · 2.67 KB
Raw

New file email notification

This is an AWS lambda function written in Go, that takes S3 object creation events and sends a templated email using AWS SES to a specified recepient. The email includes a presigned link to the object in S3.

Deployment using AWS SAM

The aws-serverless directory includes a template and config to deploy this app using the AWS Serverless Application Model.

Prerequisites

You'll need:

  • go installed
  • AWS SAM CLI installed
  • AWS CLI credentials set-up

Usage

  1. Execute ./aws-serverless/deploy.sh -g
  2. Enter parameter values when prompted:
  • SesSendingIdentityArn The ARN of the SES domain identity that corresponds to the MailFrom address you want to use (performing the SES domain / from address validation is outside the scope of this project)
  • MailFrom The email address to send email from
  • MailTo The email address of the notification recepient (Must be 'verified' in SES if you are in the AWS Sandbox)
  • SesDestinationIdentityArn The ARN of the SES domain identity that corresponds to the MailTo address. Only required if you are in the SES Sandbox and MailTo is not covered by SesSendingIdentityArn.
  • S3Bucket The name of the S3 bucket that will invoke this lambda function
  1. When the stack has finished deploying, it will show the LambdaARN in the outputs. Please set the S3 bucket to send s3:ObjectCreated:Put events to this Lambda ARN.

Notes

  • Please consider carefully how much email could be generated if you bulk create files in S3. Use prefix and suffix filters when you configure S3 events triggering this function. Be aware that although SES has limits in-place to help ensure the sending reputation of both your domains and SES itself, you should avoid generating an unnecessary large volume of mail.
  • The deployment template creates a new IAM user to use for pre-signing S3 URLs. This is necesary to ensure pre-signed URLs are valid for the required duration (it's possible to pre-sign with the lambda function's temporary session credentials, however this would cause pre-signed URLs to expire as soon as the session credentials expire)