Alternate Domains for CloudFront with custom or issued Certs

[mlgitdev]

Alternate Domains should be part of the stack for the compute, and custom or otherwise issued certificates: we use so many rules, whitelisting stuff, and big companies need such capability, especially for zero trust access; I want to add *.sub.domain.com with our certificate of course ( or issued).
I had to open tickets, weeks of evals and meetings to allow whitelisting a random FQDN. Now we are good, I don't allow our platform engineers to do click-ops, we run the stack inside AWS Control Tower AFT (terraform framework).

I'll be waiting for the updated version to update that accordingly.

[aws-khargita]

Hi @mlgitdev, thanks for creating this feature request!

Completely understand doing this in a way that is configurable on deployment is preferable to click ops in the console. Will add this to the backlog to include as optional CFN parameter for alternate domain to use with the solution.