v0.6.1

Support for passing an existing hosted zone stack name instead of a hosted zone ID.
The stack must export an output named HostedZoneId which the main site stack will use.

Full Changelog: v0.6.0...v0.6.1

v0.6.0

Changes

• Improved handling of new Route53 hosted zones
  • The script now prints the new nameservers to the terminal so that retrieving them from AWS console in unnecessary
• Cleanup and formatting of the messages printed to the terminal

Breaking Change

Re-running the ./provision script for an existing site will result in a new Hosted Zone being created in a separate stack. You'll need to point the domain name to new nameservers. You will also have to manually cleanup/delete the old hosted zone.

Note: AWS charges for hosted zones ($0.50 at the time of this release), you'll incur a charge if/when you do this

Recommendation: This is the only change, and is mostly a benefit for new stacks. If you have an existing site that's working with an earlier version, stick with v0.5.0 and don't worry about re-running this script until/unless something worthwhile gets added.

Full Changelog: v0.5.0...v.0.6.0

v0.5.0

• Serve default index.html file for directories (fixes #4)
• Added URI canonicalisation (enabled by default, opt-out via --no-canonical-uris flag)
• Added low-friction security headers (can be disabled with --no-security-headers)
• Added support for tags (with --tags flag)
• ./provision` is now POSIX compliant
• Some other small changes and refactors to both the scripts and the template

Full Changelog: v.0.4.2...v0.5.0

v0.4.1

• Re-use an existing hosted zone by passing in a hosted zone id (e.g. `./provision "example.com" --hosted-zone-id "")
• Give Cloudformation stack a custom name with --stack-name
• Fixes access to the www. subdomain - this was returning a 403 from Cloudfront

Full Changelog: v0.4.0...v0.4.1

v0.4.2

New Features

• Support for hosting on a subdomain
  The ./provision script now accepts an optional flag for --subdomain. This will create the stack at a subdomain instead of at the root domain name (with the extra www subdomain)
  e.g.
  ./provision "example.com" --subdomain "staging" will create a Cloudfront distribution for https://staging.example.com
  ./provision "example.com" will still create https://example.com and https://www.example.com

Fixes

• Fix for printing the outputs to stdout

Full Changelog: v0.4.1...v.0.4.2

v0.4.0

• New Usage instructions
• New flag for bucket name
• Fix old bucket name logic (it wasn't used in the template)
• Significant refactor of the provision script
• Automatic TLS certificate validation (no longer need to manually create DNS records)

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Changes

• Replaced the CloudFrontOriginAccessIdentity resource with OriginAccessControl for improved security and future compatibility.
• Switched to a managed cache policy (CachingOptimized) via CachePolicyId.
• Split the previous RecordSetGroup into two separate records:
  • SiteARecord (A record alias for root domain to CloudFront)
  • SiteWWWRecord (CNAME for www to root domain)
• Add a .tool-versions file to make installing aws-cli easier (e.g. with mise or asdf)
• Other minor formatting/style changes

⚠️ Breaking Changes

1. If updating an existing cloudformation stack created with this template, you might see an issue with the Route53 A record failing to create. Manually deleting the A record and re-running ./provision should make it work

Full Changelog: v0.2.1...v0.3.0

v0.2.1

Support for specifying bucket name as an optional second argument to ./provision

Full Changelog: v0.2.0...v0.2.1

v0.2.0

BREAKING CHANGES:

• New DNS verification method for Cloudfront requires different manual steps in the AWS console before the script will complete.

Full Changelog: v0.1.2...v0.2.0

v0.1.2

OAI in cloudformation

Full Changelog: v0.1.1...v0.1.2