<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on jpterry.com</title><link>/tags/aws/</link><description>Recent content in Aws on jpterry.com</description><generator>Hugo</generator><language>en</language><copyright>© John Terry</copyright><lastBuildDate>Tue, 02 Feb 2016 00:00:00 +0000</lastBuildDate><atom:link href="/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Secure, static, hosting w/ S3, CloudFront, and ACM</title><link>/2016/02/02/secure-static-hosting-w-s3-cloudfront-acm/</link><pubDate>Tue, 02 Feb 2016 00:00:00 +0000</pubDate><guid>/2016/02/02/secure-static-hosting-w-s3-cloudfront-acm/</guid><description>&lt;h2 id="static-html-is-cool-tls-is-cool"&gt;Static html is cool; TLS is cool&lt;/h2&gt;
&lt;p&gt;I think static sites are a great idea for public facing sites. It is a very
simple solution to getting content online, with very few downsides. It is
relatively secure, maintainable, scalable, and best of all, cheap.&lt;/p&gt;
&lt;p&gt;There are many tools for creating a static site. I&amp;rsquo;m using Jekyll, but there
are several options to choose from. Once you have your static site content, I
recommend hosting it in Amazon&amp;rsquo;s AWS S3. Any S3 bucket can act as a static html
host, serving the stored content up as a webpage.&lt;/p&gt;</description></item></channel></rss>