- BREAKING: Index Redirect functions have new configurations.
- BREAKING: hsts is now enabled by default
- BREAKING: Requires aws provider v3.41+
- Moved Lambda@Edge functions to CloudFront functions.
- The index redirect function now created using
index_redirect.
- NEW FEATURE: index_redirect_no_extension. Match any URL that ends in /; append /index.html. Example example.com/foo/bar => example.com/foo/bar/index.html
- Added override variables for default cache behavior cache attributes (eg. default_ttl, max_ttl, min_ttl)
- BREAKING: Allowing optional bucket policy. This will remove/recreate the existing bucket policy resource, but should have little impact. Since resources are being moved, this is considered breaking
- BUGFIX: OPTIONS is not a supported CORS verb in S3
- BUGFIX: CORS forwarded headers
- Configurable cloudfront methods using
cloudfront_allowed_methods. Valid options are "get", "get_options", "all"
- Configurable CORS rule when bucket is created by the module
- Added tagging framework
- Added example directory with a simple example including tagging
- Option for force_destroy_buckets
- Bump
versions.tf to support tf 0.14+
- Refactor bucket creation
- Default origin of CloudFront will change, but shouldn't have much impact
- BREAKING: Rename bucket resource, allow conditional creation
- BREAKING: Allow provided CloudFront OAI ID to skip creation of new OAI
- To migrate breaking changes, run:
terraform state mv module.<module-name>.aws_s3_bucket.static module.<module-name>.aws_s3_bucket.content[0]
terraform state mv module.<module-name>.aws_s3_bucket_policy.static module.<module-name>.aws_s3_bucket_policy.content
terraform state mv module.<module-name>.aws_cloudfront_origin_access_identity.oai module.<module-name>.aws_cloudfront_origin_access_identity.oai[0]
- Add bucket name to outputs