I decided to pay for a tech support plan and got help from tech support. It turns out that there was an issue with my individual account that would never have been visible in the AWS Management Console. Only AWS tech support would ever have been able to fix it.
"1. Your AWS resources have been isolated due to previous account suspension in 2015. Although you have reactivated your account in case #... in 2016, some of your resources were not un-isolated correctly and this could result in EC2 disconnection. Regarding this issue, I have requested our internal team to help, and they removed the isolation."
I'm not sure what it means for resources to be "isolated", but it obviously wasn't just a simple firewall configuration issue. If you're having a similar problem, you can't connect to your resources even with a wide-open firewall, and you've ever closed your AWS account and reopened it, then you might need to contact AWS tech support.
Thanks for posting your solution after getting it resolved through other means.
I have been working on EC2 instances without problems until 16-Sep-2020. From Sep-17 I suddenly started seeing the same issue in my account. Getting "Connection timed out" when trying to SSH in to any of the EC2 instances in my account.
I have tried all possible ways I can based on available documentations:
- Tried creating fresh instances.
- Added security group that allow connection from any IP
- Tried following all possible troubleshooting steps described in this doc (Spent lot of time on it):
But still no positive results.
After seeing your post, my problem seems so much similar to yours, but I don't think the account on which I'm working(Owned by my client) was suspended like that at some point previously. This is a freshly created account as far as I know.
I'm hoping someone at AWS support also will see this post here and respond.
I have figured out that my problem is different.
In my case my broadband ISP was blocking my outgoings on port 22. I have no clue from when my outgoing connections became the business for my ISP, and I am not yet sure whether this can be resolved without changing the ISP.
For those facing similar issue:
Try doing a port scan with Nmap to Portquiz to see which all ports are blocked by your ISP.
Here is a blog post I found helpful for doing this:
Ok, you just need to check port 22 for this specific issue, but I think it is definitely useful to be aware about all such outgoing ports where your ISP has decided to poke their nose. That will help you in future when you have to work with those ports.
EC2 instances unhealthy when created via ASG using cdk.asked 6 months ago
Connect Amazon DocumentDB Cluster from Outside Amazon VPCasked 10 months ago
Security group doesn't exist but I know it existsasked a year ago
New – VPC Reachability Analyzerasked 2 years ago
Cant launch new EB ruby env - failing on AWSEBInstanceLaunchWaitConditionasked 4 years ago
With a Security group I can't connect to EC2 instanceAccepted Answerasked 4 months ago
Adding custom cidr to ingress security group using Lambda without default vpcAccepted Answerasked 7 months ago
Created RDS database, Cannot connect via Microsoft SQL Server Studioasked 3 years ago
Default Security Group for Task DefinitionAccepted Answerasked 11 days ago
can't connect to any new ec2 instances or rds databasesasked 2 years ago