Releases: cloudposse/terraform-aws-cloudfront-s3-cdn
Releases · cloudposse/terraform-aws-cloudfront-s3-cdn
0.20.0 Allow disabling the logging bucket
what
- Allow disabling the logging bucket
why
- Allow using the CDN module and have an option to not create a logging S3 bucket
0.19.0 Empty `alias` if no `acm_certificate_arn` given
what
- Empty
aliasif noacm_certificate_arngiven
why
- If we give
aliasbut not giveacm_certificate_arn, the following error will be thrown:
Error: error creating CloudFront Distribution: InvalidViewerCertificate: To add an alternate domain name (CNAME) to a CloudFront distribution, you must attach a trusted certificate that validates your authorization to use the domain name. For more details, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-requirements
0.18.0 Fix IPv6 variables. Change AWS region for tests. Fix `enabled` logic. Update LICENSE
what
- Fix IPv6 variables
- Change AWS region for tests
- Fix
enabledlogic - Use
terraform-null-labelinstead ofterraform-terraform-label - Update LICENSE
why
- Duplicate
ipv6_enabledvariables - we need only one flag - We use
us-east-2region for Terratest now (us-west-1is very limited region) enabledlogic formodule "dns"was wrongterraform-null-labelhas more features and works without issues in TF 0.12
0.17.0 Add optional support for IPv6 DNS records
what
- Add optional support for IPv6 DNS records
why
- Allow creating IPv6 DNS records for the CloudFront distribution
related
- Closes #64
0.16.0 Make `ssl_support_method` empty when using CloudFront default certificate
what
- Make
ssl_support_methodempty when using CloudFront default certificate
why
- The current implementation always uses "sni-only" as
ssl_support_methodinviewer_certificateconfiguration.
According to Terraform documentation this option is required only when usingacm_certificate_arnoriam_certificate_id.
This leads to a situation where Terraform tries to setssl_support_methodto "sni-only" at each run spending several time trying to do it (~10 minutes) without effectively setting anything (it doesn't fail though).
With this commit we check the value ofacm_certificate_arnand set the properssl_support_methodonly if such value is defined and not if we are using CloudFront default certificate
0.15.1 Fix link to examples in README
what
- Fix link to examples in README
why
- Dead link
0.15.0 Add support for website config on origin
what
- Add support for website config on origin
why
- Configure S3 origin as Static website hosting
related
- Closes #14
0.14.0 Add AES256 Server Side Encryption
what
- Add AES256 Server Side Encryption
why
- Allow to encrypt s3 buckets even when not entirely necessary just for uniformity for security audits
related
- Closes #54
0.13.0 Add `aliases` to outputs
what
- Add
aliasesto outputs
why
- In the CORS settings of some other modules, it would be nice to easily get all aliases that a CF distribution made through this module controls
related
- Closes #56
0.12.0 Allow removing `origin` from the origin label
what
- Allow customizing attributes for the origin and logs bucket
why
- Allow customizing the last part of the s3 origin bucket name
- Allow customizing the last part of the s3 logs bucket name
related
- Closes #57