You can reach me @ AWS SES email forwarding

Today it’s all about communication !

Of course I will publish some content, but I also want to be reachable. I might look into the activation of “Disqus” later but I tought about enabling some sort of email communication channel first for my new domain “hikencloud.com”. If you have read the previous post, you know I don’t plan much on managing server and I am somehow fan of AWS. My domain was registered and is managed by AWS. Unfortunately, AWS doesn’t provide any “cheap” email forwarding capabilities. Well not something I can activate in a Console click.

I started to look around for possible solutions and quickly came across a posts describing how to do it with Amazon SES, Amazon S3, and AWS Lambda. This sounds like a solution aligned with my previous choice to build this blog on Jekyll.

I looked a bit more and found this article describing how to do this via the AWS CLI. In this stepped approach, there is a lot of “AWS ressource IDs” to paste from one command to the other … mmm. I’ll tell you something. I am more a fan of Terraform.

Then I made a huge mistake that I must confess here. I forgot to check if there was already an implementation of that solution in an existing module. I was so excited to produce a first piece of code to share that I directly jumped into the translation of the stepped procedure into a Terraform module.

The result of this work is now published on my Github

I doubt the project will have much success as it is already surpassed by:

• https://github.com/cloudposse/terraform-aws-ses-lambda-forwarder
• https://github.com/alemuro/terraform-aws-ses-email-forwarding
• …

My code is not nicer. It is maybe a bit simpler to follow if you are new to Terraform, specially because I kept some reference to the steps described in the original article. It’s working and you can customize it easily if you like.

I used it to enable an email communication channel between YOU and me, feel free to get in touch using blog@hikencloud.com.