1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
We managed to get them "resolved"; at least whatever seemingly irrelevant things I did managed not to trigger this bug.
- I went to the Client VPN endpoint settings and found that there were some lingering security group associations that show up in GuI but the underlying SG is already gone. I deleted those SGs.
- Turn logging settings off and then back on again
Those actions do not seem to be directly related to AWS not being able to resolve VPN endpoint DNS -- but somehow correlated with the fixes.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 3 ans