3 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi, Few additional things to check:
- Does your ec2 instance have a public IP address?
- Do you have an internet gateway attached to your VPC and does the subnet where the instance is located have a route to the internet gateway?
- Do you have any non-defauly Network access control lists that might be blocking traffic?
beantwortet vor einem Jahr
0
- yes.
- yes. Default vpc and have subject with route table and attached igw
- Not default custom SG with ssh,https,http, and custom tcp port configured, I had tried default SG it also wont work.
beantwortet vor einem Jahr
0
Is the subnet where the instance is located associated to the route table where you have the IGW attached? Do you have a specific IP address in the security group for the source(i.e. x.x.x.x/32) for the inbound rule or do you have 0.0.0.0/0?
beantwortet vor einem Jahr
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
1.yes. 2. yes. Default vpc and have subject with route table and attached igw 3. Not default custom SG with ssh,https,http, and custom tcp port configured, I had tried default SG it also wont work.