Until recently I used the web-interface of Route 53, the AWS DNS service, to manage the DNS records for my startup, ParrotPolls. Making manual changes to such a critical piece of infrastructure always made me nervous. I knew there was a better way, but I had never taken the time to set this up.
The incident which got me to set up terraform (a command-line tool for managing cloud infrastructure) was when I realized I was about to lose track of which DNS records serve which purpose. We had been trying a couple of different service providers, and in particular the email-providers usually require setting up TXT and CNAME records for DKIM and SPF. If I had used an infrastructure-as-code-approach, like terraform, I could have just looked at the history of the git-repo. That’s what I want!