2 個答案
- 最新
- 最多得票
- 最多評論
1
- Make sure of the routing of the EC2 subnet route table, if the EC2 is in private subnet (has only private IP address) then make sure it has a default route to the NAT Gateway, or if the EC2 is in public subnet (has a public IP address) then make sure it has a default route to the Internet Gateway.
- Make sure of the security group and the ACLs are not blocking the traffic.
- If the above does not resolve the issue, then enable VPC flow logs and see how the traffic flow https://docs.aws.amazon.com/vpc/latest/userguide/working-with-flow-logs.html
已回答 9 個月前
0
The screenshot shows you can get in okay, is this directly by RDP over the internet to the public IP, or another method (e.g. bastion host, peered VPC, Direct Connect, or others)?
The route table for the subnet in which the Windows instance is provisioned would be the best place to start looking, extensive advice on how to troubleshoot and what to look out for is in https://repost.aws/knowledge-center/troubleshoot-vpc-route-table
As @Matt_E says, also check outbound security group rules, and if you're not getting anywhere then turn on VPC flow logs.
相關內容
- 已提問 7 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 個月前