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
The new CAA record is supported by AWS Route53 but not considered a valid type by terraform. CAA is used to whitelist which certificate authorities are authorized to issue SSL certificates for your domain. It is quite new and was only added to AWS on August 21, 2017. CAs are expected to start enforcing it in September 2017.
This issue has been automatically migrated to hashicorp/terraform-provider-aws#1632 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
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.
ghost
locked and limited conversation to collaborators
Apr 7, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The new CAA record is supported by AWS Route53 but not considered a valid type by terraform. CAA is used to whitelist which certificate authorities are authorized to issue SSL certificates for your domain. It is quite new and was only added to AWS on August 21, 2017. CAs are expected to start enforcing it in September 2017.
Terraform Version
Terraform v0.10.4
Terraform Configuration Files
Expected Behavior
terraform plan should work
Actual Behavior
terraform plan returns error on resource type:
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
terraform plan
The text was updated successfully, but these errors were encountered: