<?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 MaisonBisson</title>
    <link>https://maisonbisson.com/tags/route53/</link>
    <description>Recent content in Route53 on MaisonBisson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 23 Sep 2018 10:24:07 -0700</lastBuildDate><atom:link href="https://maisonbisson.com/tags/route53/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>S3 and CloudFront configuration frustration</title>
      <link>https://maisonbisson.com/post/s3-and-cloudfront-configuration-frustration/</link>
      <pubDate>Sun, 23 Sep 2018 10:24:07 -0700</pubDate>
      
      <guid>https://maisonbisson.com/post/s3-and-cloudfront-configuration-frustration/</guid>
      <description>&lt;p&gt;It turns out that the interaction between S3, CloudFront, and Route53 can be bumpy when setting up buckets as CDN origins. It’s apparently expected that a CloudFront URL will read data from the wrong bucket URL &lt;em&gt;and&lt;/em&gt; redirect browsers there for the first hour or more. The message from AWS is “just wait,” which makes for a crappy experience.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
