You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously (v2.5 and earlier) this module would create ACM certs which had the certificate_transparency_logging_preference set to enabled. This made sense as the best practice recommendation from the AWS documentation says you should keep this on otherwise Chrome (as of 2018+) will not trust your certificate (see here). While that documentation just talks about Chrome, I expect other browsers will likely have followed suit since then.
My team runs Terraform in an automated environment so we picked up the recent v2.7 changes in our latest initialize and plan operations and noticed this has now been set to disabled by default. This forces a recreation of the ACM resources. This is because the newly added certificate_transparency_logging_preference input variable defaults to false.
# module.load_balancer.module.acm_lb.aws_acm_certificate.this[0] must be replaced
+/- resource "aws_acm_certificate""this" {
...
~ options {
~ certificate_transparency_logging_preference = "DISABLED" ->"ENABLED"# forces replacement
}
# other validation resources will be recreated too
We've now manually added the variable and set it to true to our deployment project to get no changes to our deployed infrastructure.
Changing the default value of certificate_transparency_logging_preference to true has some benefits:
certs do not need to be recreated for people who were using this module pre v2.5
the module follows cert best practice by default
Would we be able to get this done?
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Hi there,
Previously (v2.5 and earlier) this module would create ACM certs which had the
certificate_transparency_logging_preference
set to enabled. This made sense as the best practice recommendation from the AWS documentation says you should keep this on otherwise Chrome (as of 2018+) will not trust your certificate (see here). While that documentation just talks about Chrome, I expect other browsers will likely have followed suit since then.My team runs Terraform in an automated environment so we picked up the recent v2.7 changes in our latest initialize and plan operations and noticed this has now been set to disabled by default. This forces a recreation of the ACM resources. This is because the newly added
certificate_transparency_logging_preference
input variable defaults tofalse
.We've now manually added the variable and set it to true to our deployment project to get no changes to our deployed infrastructure.
Changing the default value of
certificate_transparency_logging_preference
totrue
has some benefits:Would we be able to get this done?
The text was updated successfully, but these errors were encountered: