1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
The issue was that containers were allowed to (re)spawn in any subnet in the VPC (I think it's random?).
Some of these had configurations which were not suitable for our services - traffic could get in, but services were not permitted to respond. Confirmed by spawning a bunch of containers and seeing which ones I can access.
The solution is to recreate the services with more carefully selected subnets.
con risposta un mese fa
Thanks for sharing the solution!
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Can you elaborate more about the networking configuration? Like, what is the default gateway configured? What about the SG and the NACL rules? What is the error that you are receiving when you are unable to connect to the public IP (please, provide the curl -vI output).