<?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 Tibor Hercz - Writing about Cloud, architecture, AWS, GCP and software engineering.</title>
    <link>https://tiborhercz.com/tags/route53/</link>
    <description>Recent content in Route53 on Tibor Hercz - Writing about Cloud, architecture, AWS, GCP and software engineering.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 31 Jan 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tiborhercz.com/tags/route53/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>S3 website: Why your domain and bucket name must be identical</title>
      <link>https://tiborhercz.com/s3-website-why-your-domain-and-bucket-name-must-be-identical/</link>
      <pubDate>Mon, 31 Jan 2022 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/s3-website-why-your-domain-and-bucket-name-must-be-identical/</guid>
      <description>&lt;p&gt;When setting up S3 website hosting you can use a Route53 alias for connecting the domain to the website bucket.&#xA;This approach forces you to set identical names for the S3 bucket and domain name.&#xA;In this article I will explain to you why the domain name and bucket names must be identical.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
