1回答
- 新しい順
- 投票が多い順
- コメントが多い順
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.
回答済み 1ヶ月前
Thanks for sharing the solution!
関連するコンテンツ
- 質問済み 3年前
- AWS公式更新しました 1年前
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).