-
Notifications
You must be signed in to change notification settings - Fork 0
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
Basic AWS SES Implementation #77
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General Question - does this not require some sort of API Key?
Also - can you have a look at the SendGrid implementation for "enforced emails" they're a bit more complicated these days (and at some point I may add the extra complexity that I added into Buynex..... |
No. When running on AWS infra, it relies on IAM grants to be allowed to talk to SES. If you're running locally, then it utilises SSO via the AWSSDK (which you configure a profile setting in a particular appsettings key) |
@nickskliar-davies you can also it seems pass in general AWS Access Key and Secret in addition to the SSO/verified role identity etc. Not sure whether we need to support that or not. |
@dcsl-alexis I mean, in an ideal world yes, but if that's more work than you have time for, use a docstring or something to say we only support the integrated auth OWTTE. |
Recently implemented email sending via SES on a project - contributing this back for future use in Obelisk based projects.