invalid or unknown key: ssl_certificate_id for ACM certs

[hashibot]

This issue was originally opened by @DevilWAH as hashicorp/terraform#15550. It was migrated here as a result of the provider split. The original body of the issue is below.

---

PROVIDER ISSUES

PLEASE NOTE: Terraform has split out the builtin Providers into their own repositories. For any Provider issues, please open all issues and pull requests in the corresponding repository. An index of supported Providers can be found here:

• https://github.com/terraform-providers

All other issues (that appear to affect multiple or all providers) may be an issue with Terraform's core, and should be opened here.

---

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
0.9.11

Terraform Configuration Files

resource "aws_alb_listener" "alb-listner-enforcement-int-web-443" {
  load_balancer_arn = "${aws_alb.alb-enforcement-int-web.arn}"
  port              = "443"
  protocol          = "HTTPS"
  ssl_certificate_id = "arn:aws:acm:eu-west-2:321633319430:certificate/846353d3-39cc-47b4-ac02-cc9c380f7fd3"

  default_action {
    target_group_arn = "${aws_alb_target_group.alb-tg-enforcement-int.arn}"
    type             = "forward"
  }
}

Debug Output

• aws_alb_listener.alb-listner-enforcement-int-web-443: : invalid or unknown key: ssl_certificate_id

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

I would expect it to apply the cert to the alb listener, however it does not seem to work for certs in the ACM only those stored in IAM.

Actual Behavior

It fails and reports it can't find an existing cert.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply or terraform Plan when you have an aws_alb_listener using https and you attempt to attach a cert that is stored in ACM.

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Make aws_iam_policy_attachment warning less opaque #1234

[ju2wheels]

@DevilWAH are you sure this is the right resource parameter? Shouldnt ssl_certificate_id be certificate_arn instead https://www.terraform.io/docs/providers/aws/r/alb_listener.html ?

[Ninir]

Hey folks,

@DevilWAH: @ju2wheels is correct on that, the attribute that should be used is certificate_arn.
Could you check and tell us how it goes?

Would like to close this one if it's not an issue :)

[paddycarver]

Hi there! It looks like the issue author hasn't replied in a while. In the interest of helping keep the repository clean to help identify the issues that require maintainers' attention, I'm going to close this issue out. If it still requires action, or if someone has interest in it being reopened, feel free to reply to the issue.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!