Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "How to trigger lambda function when an email received through SES" #97

Open
ZooeyMiller opened this issue Jul 12, 2017 · 8 comments

Comments

@ZooeyMiller
Copy link

With regards to dwyl/apprenticeship#13 (comment) we want to add a section to this repo explaining how to trigger a lambda function when an email is received with SES.

@finnhodgkin
Copy link
Contributor

@ZooeyMiller
Copy link
Author

In order to set up SES we need to have a domain to use. I've been meaning to get one for a personal website for a while so am sorting that out through namecheap right now.

@ZooeyMiller
Copy link
Author

ZooeyMiller commented Jul 12, 2017

there has been a problem with namecheap double charging me and not giving me the domain so currently dealing with their support chat to try and get this sorted, as as far as I understand it is a prerequisite for setting up SES.

EDIT: all sorted now

@ZooeyMiller
Copy link
Author

Having updated the DNS records on my domain we're now waiting for them to be verified by Amazon which it says can take up to 72hrs, so we pretty much have to wait on that.

@finnhodgkin
Copy link
Contributor

Dropping 'in-progress' and the time estimate until the domain is verified and we can continue to work on this.

@finnhodgkin
Copy link
Contributor

The domain is now verified so we should be able to work on this tomorrow 👍

@ZooeyMiller
Copy link
Author

We're back on this now that AWS have approved the domain.

@ZooeyMiller
Copy link
Author

We have now set up a lambda function to be triggered when an email is received via SES, but it is hard to tell if the function is actually running as it currently doesn't do anything meaningful.

As detailed in dwyl/apprenticeship#13 (comment) we are going to get started with #98 as these two issues link together, and if the lambda function being triggered by the email saves to S3 then we can easily verify that it is working.

Taking off time estimate for now, will go back on when we start writing the documentation, TE will go on #98 while we are working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants