Amazon-Web-Services – Communication between VPC subnet instances

By Silicon Valley

I am trying to set up a very simple VPC environment, but I am having trouble getting the instances in the subnet to see each other: ie, when I ping 10.0.0.10 from 10.0.0.93 It did not succeed.

I think this is a problem of some misconfiguration, but after reviewing everything I can’t find the problem.

This is my route table ( Default):

rtb-14f2127c, 1 Subnet, No, vpc-1ef21276 (10.0.0.0/16)
rtb-10f21278, 0 Subnets, Yes, vpc -1ef21276 (10.0.0.0/16)

There is only one DHCP option:

dopt-12f2127a domain-name-servers = AmazonProvidedDNS;

My network ACL (inbound):

100 ALL ALL 0.0.0.0/0 ALLOW
* ALL ALL 0.0.0.0/0 DENY
 pre> 
(Outbound):
 
 
100 ALL ALL 0.0.0.0/0 ALLOW
* ALL ALL 0.0.0.0/0 DENY


My security group has (inbound):




ALL sg-b3637adf 
22 (SSH) 0.0.0.0/0 
80 ( HTTP) 0.0.0.0/0 
443 (HTTPS) 0.0.0.0/0 
4848 0.0.0.0/0 
8080 (HTTP*) 0.0.0.0/0 
8258 0.0 .0.0/0 
24848 0.0.0.0/0 
28009 0.0.0.0/0 
28080 0.0.0.0/0 
28181 0.0.0.0/0


(Outbound):




ALL 0.0.0.0/0
 22 (SSH) 0.0.0.0/0 
80 (HTTP) 0.0.0.0/0 
443 (HTTPS) 0.0.0.0/0 
8080 (HTTP*) 0.0.0.0/0 < br />8258 0.0.0.0/0 
28009 0.0.0.0/0 
28080 0.0.0.0/0 
28181 0.0.0.0/0


Thank you,
Andrea
I solved this problem: I added (including entering Station and outbound) 

ALL sg-b3637adf

I fixed the security group ID (sg-b3637adf) issue.

Perform these two steps to enable the instance to ping itself.

For future readers, if your ICMP port is blocked by a security group, you will not be able to ping. Make sure there are rules in the security group Allow all ICMP access.

I’m trying to build a very simple VPC environment, but I’m having trouble getting the instances in the subnet to see each other: that is, when I When pinging 10.0.0.10 from 10.0.0.93, it was not successful.

I think this is a problem of some misconfiguration, but after reviewing everything I can't find the problem.

< p>This is my route table (default):

rtb-14f2127c, 1 Subnet, No, vpc-1ef21276 (10.0.0.0/16)
rtb -10f21278, 0 Subnets, Yes, vpc-1ef21276 (10.0.0.0/16)

There is only one DHCP option:

dopt-12f2127a domain-name -servers = AmazonProvidedDNS;

My network ACL (inbound):

100 ALL ALL 0.0.0.0/0 ALLOW
* ALL ALL 0.0.0.0/0 DENY
 
(Outbound):
 
 
100 ALL ALL 0.0.0.0/0 ALLOW
* ALL ALL 0.0.0.0/0 DENY


My security group has (inbound):




ALL sg-b3637adf 
22 (SSH) 0.0.0.0/0 
80 ( HTTP) 0.0.0.0/0 
443 (HTTPS) 0.0.0.0/0 
4848 0.0.0.0/0 
8080 (HTTP*) 0.0.0.0/0 
8258 0.0 .0.0/0 
24848 0.0.0.0/0 
28009 0.0.0.0/0 
28080 0.0.0.0/0 
28181 0.0.0.0/0


(Outbound):




ALL 0.0.0.0/0
22 (SSH) 0.0.0.0/0 
80 (HTTP) 0.0.0.0 /0 
443 (HTTPS) 0.0.0.0/0 
8080 (HTTP*) 0.0.0.0/0 
8258 0.0.0.0/0 
28009 0.0.0.0/0 < br />28080 0.0.0.0/0 
28181 0.0.0.0/0


Thank you, 
Andrea




< p>I solved this problem: I added to the security group (including inbound and outbound) 




ALL sg-b3637adf


I fixed the security group ID (sg-b3637adf).


Perform these two steps to enable the instance to ping itself.


For future readers, if your ICMP port You will not be able to ping the blocked security group. Make sure that there are rules in the security group that allow all ICMP access.
, , , , , ,

Leave a Comment

Your email address will not be published.