Guide to using AWS Lambda with AWS Simple Email Service #99

finnhodgkin · 2017-07-13T17:35:58Z

** Probably not ready for merge because the advice on permissions for S3 is a little dubious... Currently we just open it to anyone and everyone **

Adds a section on Amazon Simple Email Service

Relates to #97 #98

…97 #98

codecov · 2017-07-13T17:35:59Z

Codecov Report

Merging #99 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #99   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         230    230           
=====================================
  Hits          230    230

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf0aef1...ba7b80a. Read the comment docs.

codecov · 2017-07-13T17:35:59Z

Codecov Report

Merging #99 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #99   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         230    230           
=====================================
  Hits          230    230

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf0aef1...96fff16. Read the comment docs.

nelsonic · 2017-07-16T16:29:24Z

@finnhodgkin only just saw this. 😮
(if PR isn't assigned to me then I don't get a notification for it...) 🔕 😞

nelsonic · 2017-07-16T16:40:24Z

README.md

@@ -77,6 +77,7 @@ something to S3 on each execution cycle you could rack up the bill!
 * [Use the callback parameter with node v4.3](#the-callback-parameter)
 * [Trigger a Lambda function using an event from DynamoDB](#triggering-a-lambda-function-using-an-event-from-dynamodb)
 * [Trigger a Lambda function using the Simple Notification System](#trigger-a-lambda-function-using-the-simple-notification-system)
+* [Trigger a Lambda function when an email comes in to the AWS Simple Web Service](#trigger-a-lambda-function-when-an-email-is-received-by-amazon-simple-email-service)


AWS Simple Web Service >> AWS Simple Email Service (SES)

nelsonic · 2017-07-16T16:41:52Z

README.md

+#### Save the email to S3
+Go back to the rule set you created for your Lambda function. Add a new action to it, this one should be an S3 action, with the bucket you want to use selected. This will save the email to S3. Make sure this action is positioned **above** your Lambda function:
+
+![ses management console - google chrome_006](https://user-images.githubusercontent.com/22300773/28177094-a0e16bfc-67f1-11e7-8676-feabc437295f.png)


try to avoid having other tabs in the screenshot as it's "noisy".

(keep the focus on the task you are currently performing to avoid distracting/confusing your reader) 😉

I don't have access to Photoshop here and the Linux alternatives are a bit of a pain to use. Happy to update this when I get home from my holiday 🍹

nelsonic · 2017-07-16T16:43:04Z

README.md

+            "Action": [
+                "logs:CreateLogStream",
+                "logs:PutLogEvents",
+                "s3:*" // This allows all S3 functions


fairly certain these comments aren't allowed. (which is a shame because they are instructive ...)

nelsonic · 2017-07-16T16:48:30Z

README.md

+
+So now when we receive an email it is save to S3 and a function is triggered. Next we need we need to hook the two up so our Lambda function reads the saved file, and saves the body in a nice readable way.
+
+#### Save the body to S3 using AWS Lambda


If we save all incoming emails it's possible for a SPAMer to flood our Lambda and cause us to waste loadz-a-money on S3 writes ...

$0.05 per 1,000 writes to S3 might not sound like a lot, but it will add up if you consider the volume of spam sent/received. (if you use GMail you won't realise it because Google has amazing filters, but an "un-protected" email address will get hundreds and a reasonably popular domain will get thousands of SPAM emails per day)

Fun Fact: Over 50% of email is SPAM see: https://www.statista.com/statistics/420391/spam-email-traffic-share/

I've added a note with some of the above comment before the S3 section. Should hopefully help to deter people from leaving this set up on their own accounts.

A better exercise could be to process the email with Lambda before saving to S3 so we could run something more interesting like a check for a certain keyword or something like that.

nelsonic

@finnhodgkin & @ZooeyMiller so far looks good. just need to update the TOC then should be ready to merge. thanks! 🎉

codecov · 2018-11-01T03:06:43Z

Codecov Report

❗ No coverage uploaded for pull request base (master@bf0aef1). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master    #99   +/-   ##
=======================================
  Coverage          ?   100%           
=======================================
  Files             ?      5           
  Lines             ?    230           
  Branches          ?      0           
=======================================
  Hits              ?    230           
  Misses            ?      0           
  Partials          ?      0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf0aef1...2893433. Read the comment docs.

nelsonic

@finnhodgkin thank you for making the time to complete this PR even though it's not your current focus! I really appreciate it! 🥇
Hope you have a great day! ☀️

adds a basic guide to calling Lambda functions on incoming mail (ses) #…

ba7b80a

…97 #98

finnhodgkin added help wanted in-progress labels Jul 13, 2017

ZooeyMiller added awaiting-review and removed help wanted in-progress labels Jul 13, 2017

ZooeyMiller requested a review from nelsonic July 13, 2017 17:37

finnhodgkin changed the title ~~[WIP] Guide to using AWS Lambda with AWS Simple Email Service~~ Guide to using AWS Lambda with AWS Simple Email Service Jul 13, 2017

fix hash link to SES section. #97

96fff16

nelsonic added in-review and removed awaiting-review labels Jul 16, 2017

nelsonic self-assigned this Jul 16, 2017

nelsonic reviewed Jul 16, 2017

View reviewed changes

nelsonic removed the in-review label Jul 16, 2017

nelsonic assigned finnhodgkin and unassigned nelsonic Jul 16, 2017

nelsonic mentioned this pull request Jul 17, 2017

Write fixture with multiple names and emails. dwyl/email#14

Closed

nelsonic added help wanted in-progress labels Oct 29, 2018

Updates TOC typo and adds warning to the S3 part of the SES section #99

2893433

finnhodgkin assigned nelsonic and unassigned finnhodgkin Nov 1, 2018

nelsonic added awaiting-review and removed in-progress labels Nov 1, 2018

nelsonic approved these changes Nov 7, 2018

View reviewed changes

nelsonic merged commit 1a1448c into master Nov 7, 2018

nelsonic deleted the aws-ses branch November 7, 2018 09:05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Guide to using AWS Lambda with AWS Simple Email Service #99

Guide to using AWS Lambda with AWS Simple Email Service #99

finnhodgkin commented Jul 13, 2017 •

edited

Loading

codecov bot commented Jul 13, 2017

codecov bot commented Jul 13, 2017 •

edited

Loading

nelsonic commented Jul 16, 2017

nelsonic Jul 16, 2017

nelsonic Jul 16, 2017 •

edited

Loading

finnhodgkin Nov 1, 2018

nelsonic Jul 16, 2017

nelsonic Jul 16, 2017 •

edited

Loading

finnhodgkin Nov 1, 2018

nelsonic left a comment

codecov bot commented Nov 1, 2018

nelsonic left a comment


		So now when we receive an email it is save to S3 and a function is triggered. Next we need we need to hook the two up so our Lambda function reads the saved file, and saves the body in a nice readable way.

		#### Save the body to S3 using AWS Lambda

Guide to using AWS Lambda with AWS Simple Email Service #99

Guide to using AWS Lambda with AWS Simple Email Service #99

Conversation

finnhodgkin commented Jul 13, 2017 • edited Loading

codecov bot commented Jul 13, 2017

Codecov Report

codecov bot commented Jul 13, 2017 • edited Loading

Codecov Report

nelsonic commented Jul 16, 2017

nelsonic Jul 16, 2017

Choose a reason for hiding this comment

nelsonic Jul 16, 2017 • edited Loading

Choose a reason for hiding this comment

finnhodgkin Nov 1, 2018

Choose a reason for hiding this comment

nelsonic Jul 16, 2017

Choose a reason for hiding this comment

nelsonic Jul 16, 2017 • edited Loading

Choose a reason for hiding this comment

finnhodgkin Nov 1, 2018

Choose a reason for hiding this comment

nelsonic left a comment

Choose a reason for hiding this comment

codecov bot commented Nov 1, 2018

Codecov Report

nelsonic left a comment

Choose a reason for hiding this comment

finnhodgkin commented Jul 13, 2017 •

edited

Loading

codecov bot commented Jul 13, 2017 •

edited

Loading

nelsonic Jul 16, 2017 •

edited

Loading

nelsonic Jul 16, 2017 •

edited

Loading