<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Stefan Ukena's Blog</title><link>https://blog.ukena.de/tags/devops/</link><description>Recent content in Devops on Stefan Ukena's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.ukena.de/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>How To Import Your Aws Route 53 Records To Terraform</title><link>https://blog.ukena.de/posts/import-route53-settings-to-terraform/</link><pubDate>Thu, 16 Apr 2020 00:00:00 +0000</pubDate><guid>https://blog.ukena.de/posts/import-route53-settings-to-terraform/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The incident which got me to set up &lt;code&gt;terraform&lt;/code&gt; (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 &lt;code&gt;terraform&lt;/code&gt;, I could have just looked at the history of the git-repo. &lt;em&gt;That&amp;rsquo;s what I want!&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>