Why I'm building an interface to AWS SES?

tl; dr; - AWS SES, Amazon's transactional email service, does its core job of delivering emails but its UI sucks so I'm trying to solve that.

I manage a small startup's AWS infrastructure and a lot of our support issues center around our email - changing the template, adding a new template, being able to test a template prior to going live with it and so on. As you can see from this non-exhaustive list, these are issues that ops should be able to handle themselves.

Unfortunately, while AWS SES has command line tools for everything, only a power user can be expected to use them to self service their own issues.

So, to get around this, I built https://zeer0.com. Right now, you can use to view your SES email templates online @ https://zeer0.com/templates - you will need an AWS key and secret - but I plan to add more features and make this offering more robust.