Open bmillwood opened 3 weeks ago
It turns out that actually the SES lambda handler doesn't receive the e-mail body (docs). So you do have to set up email -> SNS -> lambda after all.
Instead I'm going to try email -> SNS -> SQS -> meddler, so maybe I don't need a lambda at all
AWS docs
You can receive e-mails to lambda, S3, or SNS (or some other weird alternatives). SNS doesn't help you get it into code, since the way to do that is to just add a lambda handler to the SNS topic anyway. (You can also have SNS topic subscriptions via http or https, which isn't ideal because the endpoint has to be public, or email, SMS, or SQS, none of which I think help). S3 would (afaict) require polling rather than being notified.
So you have a lambda, which can then pass on the message. In the name of avoiding having to package dependencies with the lambda, I may want to run an http server on the meddler binary and use the python builtin
http.client
module to send the data there. I can hopefully set up the network configuration so that only the lambda can reach the relevant port.