EC2 unable to connect to 1.1.1.1

So in our case , when they are in same subnet , how should we create the route to internet gateway?

Does that mean EC2 and NAT Gateway are in the same subnet? I think that communication will probably not be possible even if the route to the Internet gateway and the route for the public access NAT Gateway are set in the same route table. Therefore, if you want to go through NAT Gateway, you will need to start EC2 in a private subnet and set a route to NAT Gateway in the route table.

Can u explain me why NAT should go through Internet gateway, why can’t this route the traffic alone

An internet gateway is linked to a VPC, but a NAT gateway is created within a subnet. The Internet gateway is your VPC's only gateway to the public network. If there is no Internet gateway, the VPC will lose the gateway to communicate with the public network, so even if there is a NAT Gateway, it will not be possible to communicate with the public network. https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html

Public – (Default) Instances in private subnets can connect to the internet through a public NAT gateway, but cannot receive unsolicited inbound connections from the internet. You create a public NAT gateway in a public subnet and must associate an elastic IP address with the NAT gateway at creation. You route traffic from the NAT gateway to the internet gateway for the VPC. Alternatively, you can use a public NAT gateway to connect to other VPCs or your on-premises network. In this case, you route traffic from the NAT gateway through a transit gateway or a virtual private gateway.