> This flow was designed to take advantage of the S3 trigger system and break each action into a small Lambda.
The email flows from S3 => Lambda => SES so the underlying design seems to prohibit sending of emails directly from SES.
It sounds like SES could still be used directly, but you then need to add in authorization and user management if you're accessing it externally.
It's a cool project and I can envision it being used for internal tooling for automated email notifications or something of that nature. Just doesn't seem practical for users.
The email flows from S3 => Lambda => SES so the underlying design seems to prohibit sending of emails directly from SES.
It sounds like SES could still be used directly, but you then need to add in authorization and user management if you're accessing it externally.
It's a cool project and I can envision it being used for internal tooling for automated email notifications or something of that nature. Just doesn't seem practical for users.