From ccedadc9ac8eb1b6ba5a1702002148c9306eda74 Mon Sep 17 00:00:00 2001 From: Thomas Bruun Date: Wed, 27 Apr 2016 16:02:43 +0200 Subject: [PATCH] AWS ELB Listener: Clarify that ssl_certificate_id must be ARN (#6370) Just saying `id` is ambiguous, it could be interpreted as the resource ID which will fail with the follow error: `CertificateNotFound: Server Certificate not found for the key: `. The AWS documentation states that the ssl certificate id parameter must be the ARN. --- website/source/docs/providers/aws/r/elb.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/providers/aws/r/elb.html.markdown b/website/source/docs/providers/aws/r/elb.html.markdown index 5c644fe90..b8efdee52 100644 --- a/website/source/docs/providers/aws/r/elb.html.markdown +++ b/website/source/docs/providers/aws/r/elb.html.markdown @@ -96,7 +96,7 @@ Listeners support the following: * `lb_port` - (Required) The port to listen on for the load balancer * `lb_protocol` - (Required) The protocol to listen on. Valid values are `HTTP`, `HTTPS`, `TCP`, or `SSL` -* `ssl_certificate_id` - (Optional) The id of an SSL certificate you have +* `ssl_certificate_id` - (Optional) The ARN of an SSL certificate you have uploaded to AWS IAM. **Only valid when `lb_protocol` is either HTTPS or SSL** Health Check supports the following: