1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
In step 4 of the instructions, update the hostname server i.e.
./easyrsa build-server-full server nopass
to a FQDN eg
./easyrsa build-server-full server.domain.tld nopass
Then it appears in ACM and VPN Endpoint configuration.. I do believe you can use any domain name you wish. In Step 7, you do not need to import a Client Cert into ACM. Just reference the Server Cert
Any subsequent clients you create, ensure you use the same domain name as in Step 5
I have provided feedback to the Documentation above too. Hopefully it will be adjusted
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 8 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
I swear I tried this before and didn't get a domain name. I updated the script I developed to create the certs and store the values in Parameter store and today the cert has a FQDN. It appears the FQDN is required for the creation of the cert. As to the documentation don't forget to update the script that does the cp commands to use the FQDN instead of server.crt/key.
Thanks for the help.