Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The certificate that is attached to your distribution doesn't cover the alternate domain name (CNAME) that you're trying to add
See original GitHub issue🐛 Bug Report
What is the problem?
Ran into a bunch of issues running https://github.com/aws-samples/aws-cdk-examples/tree/master/typescript/static-site/
Last one being
The certificate that is attached to your distribution doesn’t cover the alternate domain name (CNAME) that you’re trying to add
Reproduction Steps
cdk deploy -c domain=webconverger.com -c subdomain=talks
Verbose Log
https://s.natalian.org/2019-08-14/cdk.txt
I already have a *.webconverger.com certificate issued arn:aws:acm:us-east-1:407461997746:certificate/5efcc663-6e6c-43b3-bab0-49ad36b27152 so I am a little puzzled why it is:
- creating a webconverger.com one instead of a talks.webconverger.com one
- not simply using the existing wildcard certificate
Environment
Archlinux user
[hendry@t480s static-site]$ git describe --always
e8d9b04
[hendry@t480s static-site]$ cdk --version
1.3.0 (build bba9914)
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m using Terraform now: https://github.com/kaihendry/dabase.com/blob/master/terraform/s3.tf
Not sure why I didn’t think of using Terraform before. It’s saner than JS/TS and being locked into a single Cloud provider.
I have managed to work round the problem. See here: https://github.com/davidsteed/awscdkstaticsite