Member-only story
Using Q To Deploy CloudFront and a TLS Certificate — Yet Another Problem With the ACM Deployment Process
Dealing with subdomains for TLS Certificates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
⚙️ A series on Security Automation. The Code.
🔒 Related Stories: Cybersecurity | Penetration Tests | AI
💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have some code that will deploy a website hosted in an S3 bucket, fronted by CloudFront with a TLS certificate. You can use it to deploy any website.
Initially, I only tested the basic domain option where only the primary domain is used to visit the website as I wrote about in the last post.
When I tried to add a website with a www record or a wildcard it failed, so fixing that in this post and a few other things.
I figured out the problem with some help from Q, which told me to go look at the certificate details. So heading over to ACM the problem is now obvious:
