aws_acm_certificate attributes reference - non existing attributes

[piontas]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

terraform -v
Terraform v0.12.20
+ provider.aws v2.46.0

Affected Resource(s)

• aws_acm_certificate

Terraform Configuration Files

# main.tf
resource "aws_acm_certificate" "cert" {
  domain_name               = "example.com"
  certificate_authority_arn = "arn:aws:acm-pca:eu-west-1:ACCOUNT_ID:certificate-authority/CERTIFICATE_ID"
  subject_alternative_names = ["something.example.com"]
  tags  = {
    SomeTag = "value"
}

  lifecycle {
    create_before_destroy = true
  }
}

# output.tf
output "certificate_arn" {
  description = "Some description"
  value       = aws_acm_certificate.cert.arn
}

Debug Output

Error: Unsupported attribute

  on outputs.tf line 4, in output "certificate_arn":
  4:   value       = aws_acm_certificate.cert.arn

Panic Output

Expected Behavior

aws_acm_certificate.cert.arn should return certificate arn

Actual Behavior

    | aws_acm_certificate.cert is empty tuple

This value does not have any attributes.

Steps to Reproduce

1. terraform apply without outputs defined. It will work and create certificate
2. define output in outputs file to be able to see certificate arn
3. Run terraform plan

Important Factoids

Certificate Authority certificate_authority_arn used in configuration is AWS ACM Private CA. It is in an Active state!
Certificate exist and it's working fine.

[mjrc]

I did have the same problem and Terragrunt did not let me execute a plan. After trying a few things such as changing Terraform version and provider version, the only thing which helped me get to a plan was to remove the resource from the state and reimport it. I've used an older provider when doing so and I did not test whether it would work on the new provider. My current versions are:

terraform -version
Terraform v0.12.20
+ provider.archive v1.3.0
+ provider.aws v2.40.0
+ provider.template v2.1.2

[priiiiit]

I had the same problem with aws_cloudfront_distribution resource complaining about change in active_trusted_signers.

Removing from state and then importing the resource once again fixed the problem. I am using Terragrunt and fixed it while using the latest Terraform, Terragrunt and AWS provider.

Versions:

$ terraform -version
Terraform v0.13.0
$ terragrunt --version
terragrunt version v0.23.33
$ tf providers
Providers required by configuration:
.
└── provider[registry.terraform.io/hashicorp/aws] ~> 3.0, ~> 3.0

Removing:

$ terragrunt state rm aws_cloudfront_distribution.website_cdn_root
[...]
Removed aws_cloudfront_distribution.website_cdn_root
Successfully removed 1 resource instance(s).
Releasing state lock. This may take a few moments...

Importing:

$ terragrunt import aws_cloudfront_distribution.website_cdn_root <CLOUDFRONT_DISTRO_ID>
[...]
aws_cloudfront_distribution.website_cdn_root: Importing from ID "<CLOUDFRONT_DISTRO_ID>"...
aws_cloudfront_distribution.website_cdn_root: Import prepared!
  Prepared aws_cloudfront_distribution for import
aws_cloudfront_distribution.website_cdn_root: Refreshing state... [id=<CLOUDFRONT_DISTRO_ID>]

After this, plan and apply worked just fine again.

[justinretzolk]

Hey y'all 👋 Thank you for taking the time to file this, and for the continued discussion! Given that there's been a number of AWS provider releases since the most recent comment, can anyone confirm whether they're still experiencing this behavior?

[gdavison]

Since there's been no response, we will assume that this issue has been resolved and will close it.

[github-actions]

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.