Implement Amazon SES Email Utility #62
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ℹ️ Issue
Closes #58
📝 Description
Added support for sending emails through Amazon SES and a verified identity. @bodhiYG added all the relevant logic needed through one of our existing projects, JPAL, while I added functioning tests and did some clean up afterwards. The util/email module is where all the email service lives including a service with the relevant methods and a controller with a test endpoint.
✔️ Verification
Running the POST endpoint through Postman yields the following result so long as the .env and recipient emails are set up properly.
🏕️ (Optional) Future Work / Notes
Once S3 is merged, we can potentially move it within the util module to have all the AWS under one place.