- 最新
- 投票最多
- 评论最多
I would check to see if any changes have been made to your instance's Security Group or the NACL assigned to the subnet. You can utilize the VPC Reachability Analyzer to troubleshoot your network traffic flow.
https://aws.amazon.com/blogs/aws/new-vpc-insights-analyzes-reachability-and-visibility-in-vpcs/
One other note - If you stop and start an instance your instance is usually deployed to different hardware. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html#what-happens-start
this problem lasted for about 30 minutes, we didn't edit Security Group or Network ACL parameters before, during the crash I was able to access the server via SSM session and I found that the server lost connection to the internet because when trying to ping and resolving some domains and IP addresses like 8.8.8.8 , 1.1.1.1 , google.com etc returned no response
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前