1 Answer
- Newest
- Most votes
- Most comments
1
Hello.
I thought it might be a spelling mistake.
Try making your template like this:
CertficateArn→CertificateArn
"Listeners": [
{ "Port": 443,
"Protocol": "https",
"Certificates": [{ "CertificateArn": { "Ref":"ParamDefaultCert" }}],
In the document below, it is "CertificateArn" and your template is "CertificateArn".
Your template is missing the "i" in "CertificateArn".
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticloadbalancingv2-listener-certificate.html
Relevant content
- asked a year ago
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
Holy Carp! I do believe that you're right about the misspelling. Thanx!
The only question I have is that CFN accepted my template last week as a String and not a JSONObject. But this week it seems to require the JSONObject (CertificateArn), which is weird.
I wonder if it's possible to see the previous version of the AWS documentation. I looked on GitHub but I can't seem to find the docs there.
Even more interesting is that CFN let me create the stack with the misspelled "CertficateArn" string! I corrected the spelling in my templates and compared them to the template in the stack and it shows the difference in spelling. WTF??!?
CFN is doing some really weird stuff this morning.
In the past, it seemed like you could see the change history of the document on GitHub, but now it seems like you can't see it. https://aws.amazon.com/jp/blogs/aws/retiring-the-aws-documentation-on-github/
It's interesting that the deployment was successful even though the spelling was incorrect.