- 최신
- 최다 투표
- 가장 많은 댓글
HI Tasio,
0.0.0.0/0 >> igw-bead07db All incoming traffic to be directed to the internet gateway
54.179.90.198/32 >> igw-bead07db External IP to internet gateway (= alternative to #1)
172.31.0.0/16 >> local (default internal route. I can't delete that one.)
Thanks Matthias
I think there's nothing wrong with routing. Have you tried with a different instance type or with SSM Session Manager as I mentioned above?
I've seen sometimes that t2.micro instances may not serve SSH connections if load in the instance is of certain importance (I can't really quantify it). Consider that t2 instances are "burstable" (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html) and you may be running out of resources to cope with the workload + SSH.
One thing to try is to SSH using AWS Systems Manager (SSM) Session Manager. If you're using Amazon Linux 2, the SSM agent is probably already installed. Have a look at the documentation to start SSH sessions over SSM.
Hello Tasio, thanks for your reply. I can't imagine that the instance runs out of resources because their is no load on it so far, except the freshly deployed Amazon Linux 2.
Is that routing correct: Destination >> Target 0.0.0.0/0 >> igw-bead07db 54.179.90.198/32 >> igw-bead07db 172.31.0.0/16 >> local ?
Could this be some timeout on the NI or on the NetworkManager in Linux? Because I even can't ping the external IP anymore after few minutes.
Many thanks Matthias
What's the second route in that table for?
What instance family and size are you running? How is the CPU/memory usage in it?
Hi Tasio,
this is a T2, micro instance. CPU/memory consumption should be ok. I have seen a spike for CPU usage up to 25% when restarting/connecting. As this is a unmodified new instance in original state (no additional packages or services installed), I think memory/CPU consumption should be ok.
Thanks Matthias
Same behavior with another new instance with SLES. Any thoughts?