1 Answer
- Newest
- Most votes
- Most comments
1
Sounds like you are able to log onto the node via SSH, but any efforts to get packages fail. Most of the time this is due to egress traffic not being able to get to the public internet.
You are on the right path to check routing, but often when this happens to me I leverage network reachability analyzer. Its super easy to use, and I find it's been an awesome tool to leverage where in the past you had to do many manual checks to perform the same.
Give it a try here. https://docs.aws.amazon.com/vpc/latest/reachability/getting-started.html
Let me know if you have any issues with this, or if it helps you then please accept my answer after you've tried it out - it would be much appreciated! Good luck :)
answered a year ago
Relevant content
- asked a year ago
- asked 2 years ago
- asked a year ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated a year ago
which path sources should i add, which ones are crucial to get analyzed, is there a certain one that will permanently resolve the issue? or do i try them all?
omg it worked, my outbound was the issue did the reachability and missed that there was no 0.0.0.0 on the rules, just added it and its working like charm, thankyou so much!
Give a peek to not just having 0.0.0.0 out... try seeking 80/443 to ANY... and even better leverage a Nat Gw to keep your private resources "more" private :) Glad you got it to work... cheers!