- 最新
- 投票最多
- 评论最多
Hi, you said you could initially connect via EC2 Instance Connect. Can you still do this from the AWS console?
If you're not able to connect at all have you tried using Session Manager?
Have you tried using a key pair to connect with SSH?
Have you tried opening up your NACLs again temporarily to diagnose which changes are causing you trouble? For just SSH purposes you should only need port 22 inbound and ports 1024-65535 outbound. Your Security Group should only need port 22 inbound, nothing outbound as it's stateful.
I would try getting back to a known-good state, undoing everything you've done since last being able to connect via EC2 Instance Connect. Also try creating another temporary EC2 instance in a different subnet with a different NACL that's fully open, and a new different Security Group with all inbound open, and verify you can connect to it. Then bit by bit make this more like your original instance until you find what breaks it.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 7 个月前
Hi, thanks for your answer. No, I can't connect via EC2 Instance Connect anymore. Session Manager gives warning: The required IAM instance profile isn't attached to the instance. You can attach a profile using AWS Systems Manager Quick Setup. Yes, I'm trying to connect via my converted-key.ppk file. With your said, I changed my NACLs as SSH 22 for inbound and 1024-65535 for outbound only. And set to my security group just SSH 22 inbound and deleted all outbound rules. Unfortunately, nothing changed.