I setup email receiving for patty at smylee.com using Amazon SES. During this project I learned that in order to decrypt messaging using SES built-in encryption, you must decrypt using an Encryption Client available only in AWS SDK for Java and Ruby. http://docs.aws.amazon.com/kms/latest/developerguide/services-ses.html#services-ses-decrypt Because of this restriction, in this code, during the s3 event message to sqs phase, the lambda function encrypts the file at rest and removes the original.
- I’ve decided to finally go back and revamp my original hugo setup which can be found in the Hugo Site Auto Generated by Lambda post. The issue with that previous setup was if I had multiple posts (markdown files), the S3 event would trigger the lambda function as many times as the number of files uploaded, when I only needed it to run once after all were uploaded. My new plan was to publish the markdowns to github and have a lambda function trigger to pull the files and put into S3.
- I was curious about the programmable Amazon IoT Dash Button and pre-ordered two buttons, thinking I might program one to give to my dad. A few weeks ago it came in (three months earlier than expected) and went through their tutorial, which sends an email with a different subject based on how you clicked the button (single, double, long). *It looks like they’ve updated that tutorial since, and will send you a text instead of an email.