amazon-web-servicesamazon-ec2amazon-vpccidr

cannot ping EC2 instance same VPC different CIDR


I'm having an issue in the following scenario:

I created a VPC then added the CIDR 192.168.0.0/16 during creation, then I created a public Subnet (192.168.1.0/24) and a private Subnet (192.168.2.0/24), I have EC2 instances running on both subnets.

Then I added a secondary CIDR to my VPC: 11.11.0.0/16, and created a new private Subnet 11.11.1.0/24 and placed a new instance in that subnet.

The issue is that I cannot ping the EC2 instance (with IP 11.11.1.108) from an EC2 instance in the public subnet (192.168.1.198).

I have checked that:

The systems I'm using for the EC2 are Win Server, I presume this is an issue related to NAT as the addresses in the 11.11.0.0/16 are publicly routable (AFAIK), then I'd need to do kind of a translation for it to work but I'm unsure how to do it and why the route for that CIDR was added to VPC's router.

Any help and/or advise is appreciated in advance!


Solution

  • The issue with this was the Windows Server 2022 firewall blocking ICMP traffic, but actually the networking works pretty well