-
Notifications
You must be signed in to change notification settings - Fork 167
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
nodejs 12 is no longer supported and ses does not have permissions to write to bucket #45
Comments
O wow, a long time has passed. I won't have time to update the CFN to support the latest language, maybe some day but not now. And regarding access, check this section: https://github.com/0x4447/0x4447_product_s3_email#manual-work there is some manual work that you have to do to make it work. |
Oh, didn't notice this repo was dead for 2 years before the last commit... Seemed like it was the solution to create custom emails without paying heftier prices over at Gmail. |
After messing with this for a bit i realized it was pretty straight forward to setup aws simple email service. Was just a couple clicks to setup the identity and dns and then set a default rule that forwards everything to an S3 bucket. I wrote a simple boto3 python script to send mail but havent tested it yet. Was waiting for my limit approval which has now come through so maybe will test it soon. I'll post it once ive tested it. |
Yes I also managed that, but the problem comes after that. Viewing your emails from That S3 bucket |
So i have built and tested a solution for that. I have a javascript front end that hits an API gateway endpoint. The Api Gateway has a lambda proxy that triggers a lambda function to read the bucket. I need a better email formatter but its functional. Lambda (Python)
Javascript website (S3 static hosted website)
|
Perhaps of interest |
I updated the lambda node version to 14 and that part deploys successfully (Not sure if the code actually works or not on node14) then the next error i get is SES does not have permissions to write to the s3 bucket. It looks like the bucket policy is there so kind of stuck on that one. I'll try to troubleshoot some more but wanted to report it in case anything immediate stands out.
The text was updated successfully, but these errors were encountered: