<?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 Opslifeuk Limited</title><link>https://opslife.co.uk/aws/</link><description>Recent content in AWS on Opslifeuk Limited</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Thu, 04 Jun 2020 23:56:07 +0100</lastBuildDate><atom:link href="https://opslife.co.uk/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Static website hosting using S3 and CloudFront</title><link>https://opslife.co.uk/aws/static/</link><pubDate>Tue, 09 Jun 2020 22:49:25 +0100</pubDate><guid>https://opslife.co.uk/aws/static/</guid><description>A note on dates: this post was written in 2020 using Terraform 0.12 and the nodejs12.x Lambda runtime. The architecture still holds up well, but if you&amp;rsquo;re following along today, check the current AWS provider docs and use a supported Lambda runtime and Terraform version. In particular, the aws_s3_bucket resource has since been split into smaller resources (aws_s3_bucket_acl, aws_s3_bucket_logging, aws_s3_bucket_website_configuration and so on).
Recently I had the chance to create a static website using S3 and CloudFront.</description></item></channel></rss>