2 Answers
0
Are you trying to SSH from outside or withing your VPC? Meanwhile, check:
- your IGW config
- your IGW is attached to the VPC
- your public subnet where you launched instance
- your network ACL
answered a month ago
0
from another previously booted normal machine within the same VPC
Is the source machine in the same subnet? Are you using the default network ACL?
Please try these:
- Check your outbound rules and make sure you're allowing return traffic (configured in the inbound rules); remember network ACL aren't stateful as SG.
- Check your subnet associations.
- For the Source & Destination (port 22) host in the same VPC, please try running the Reachability Analyzer and share the result.
- With the Source as IGW & Destination host (port 22), run the Reachability Analyzer and share the result.
answered 24 days ago
Relevant questions
Migration of EC2, EBS-Backed instances to VPC - Issues
asked 2 days agoPort 80 (HTTP) and Port 443 (HTTPS) stopped working for all my EC2 instances of ap-south-1 Region (including any new instance i launch in this region)
asked 5 months agoVPC peering with a VPC from a different AWS Organization - cost implications
Accepted Answerasked 2 years agoOregon's multiple VPC run instances ,remote connection failure
asked a month agoAnything on the roadmap for this limitation "You cannot reference the security group of a peer VPC that's in a different Region. Instead, use the CIDR block of the peer VPC."
asked 2 months agoErrors migrating EC2 classic instances to VPC
asked a month agoRedshift Enhanced VPC Routing and Cross-Region COPY and UNLOAD commands
Accepted Answerasked a month agoHybrid Instances using SSM VPC Endpoints
asked 2 years agoBare Metal instances with KVM
Accepted Answerasked 2 years agoUnable to ssh into aws ec2 instances.
asked 13 days ago
The booted machine cannot be accessed via ssh port 22, either from any Internet outside the VPC or from another previously booted normal machine within the same VPC.
Both the staging VPC and the sandbox VPC have IGWs to connect to.
In the ACL of the VPC, we allow all IP traffic from 0.0.0.0 into that VPC.
The affected VPCs are as follows.
vpc-036aa6d40506eb636 The ACL associated with it is acl-091f2e46c2fe1364a, and the IGW associated with it is igw-0ea7d09c318f7c9d3. if you select subet as subnet-07423a9f71e9eb962 or subnet- 0eabdf489f8de52d5 will not be able to connect to ssh port 22
vpc-0257a65c1dc6c094e The ACL associated with it is acl-001174d67b9e53fa5, and the IGW associated with it is igw-089e0c4f5d403dc7e. if you select subnet as subnet-0c38bafd69fcf279e or subnet- 0c4ca8b30a53e1c89 will not be able to connect to ssh port 22.
We have added port 22 to the security group to which the machine belongs when we name the machine.
Please help us to find out the cause as soon as possible, this is already having a big impact on our business.
Thanks.