1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa