2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Welp, apparently i was just able to use SAN
's feature, and it did what i needed - with just 1 certificate (*.example.com
) i covered both (*.something-1.example.com
) and (*.something-2.example.com
).
To create via AWS CLI just use :
--subject-alternative-names
argument for command aws acm request-certificate
, but it also is possible to do it via AWS web console.
con risposta un anno fa
0
The wildcard in the certificate will not cover multiple levels. You will need to create another subdomain of something.test.example.com
and add *.something.test.example.com
to the new certificate, if you want to do DNS verification. You could add the different multi-level subdomains to a certificate and use email verification without adding the various DNS subdomains.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 9 mesi fa