<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Route53 on Head for the Cloud</title>
    <link>https://headforthe.cloud/tags/route53/</link>
    <description>Recent content in Route53 on Head for the Cloud</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Mar 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://headforthe.cloud/tags/route53/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hosting a Hugo static website in AWS</title>
      <link>https://headforthe.cloud/article/hosting-a-static-blog-in-aws/</link>
      <pubDate>Tue, 07 Mar 2023 00:00:00 +0000</pubDate>
      <guid>https://headforthe.cloud/article/hosting-a-static-blog-in-aws/</guid>
      <description>&lt;p&gt;This post is part of a &lt;a href=&#34;https://headforthe.cloud/series/hosting-a-hugo-blog-in-aws&#34;&gt;series about hosting a static website&lt;/a&gt;, and I&amp;rsquo;ll be talking about the infrastructure needed to host the website in AWS, and how to deploy via infrastructure as code (IaC). In this post, we&amp;rsquo;ll use Terraform to describe the infrastructure we want to deploy&lt;/p&gt;&#xA;&lt;h2 id=&#34;our-infrastructure&#34;&gt;Our infrastructure&lt;/h2&gt;&#xA;&lt;p&gt;I use &lt;a href=&#34;https://gohugo.io&#34;&gt;Hugo&lt;/a&gt; to run this blog - it generates static HTML pages based on files written with &lt;a href=&#34;https://www.markdownguide.org&#34;&gt;Markdown&lt;/a&gt; which means that I don&amp;rsquo;t need to worry about running servers. To host this blog, I deploy several resources into an AWS account to host this blog, as shown below:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
