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

[Migrated] SES event support. #718

Open
jneves opened this issue Feb 20, 2021 · 1 comment
Open

[Migrated] SES event support. #718

jneves opened this issue Feb 20, 2021 · 1 comment

Comments

@jneves
Copy link
Contributor

jneves commented Feb 20, 2021

Originally from: Miserlou/Zappa#1818 by youcandanch

Description

Lambda has supported SES events as a trigger for quite awhile now, and there's a few folks that have requested this functionality. It's a fairly easy add; the bulk of the code here is around testing the event shape that comes in.

The one caveat here is that when AWS sends an SES message along, it doesn't send the content of the email, even if the event type is that an email was received. If you're looking for SES support when it comes to actually handling the content of received emails, you'll have to set up a SES to S3 pipeline and instead trigger off of an S3 event.

GitHub Issues

Miserlou/Zappa#1501

@siran
Copy link

siran commented Mar 30, 2024

Being able to configure Zappa settings to trigger of an SES event, rather than doing it manually on the console would be indeed nice.

It is not enough to set it to trigger from S3, since you need the information coming from SES informing why was the rule triggered as an email.

S3 is a must to be able to process the email content and to backup the email in case of issues.

Please add support.

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

No branches or pull requests

2 participants