It seems you are having trouble establishing communication between your two EC2 instances located in the east(VPC-East) and west region(VPC-West).
It looks like your main issue is you only added a route table in the VPC-East and not a route table to your VPC-West. In order to enable the flow of traffic between the VPCs using private IP addresses, you need to manually add one or more route in both VPCs. Here is AWS peering documentation that will help walk you through the steps in creating the route tables for your VPCs.
Secondly, verify your security group for the EC2 instances and the NACLs for each resource in each VPC is configured to allow traffic to the peered VPCs. Here is documentation on the proper configuration for both the security groups and NACL.
Let us know if we can be of anymore assistance!
References:  https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-basics.html  https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-security-groups.html  https://docs.aws.amazon.com/vpc/latest/peering/troubleshoot-vpc-peering-connections.html
Error no route to host - RDPasked 3 years ago
EC2 instance doesn't have access to internetasked 3 years ago
Subdomain redirection to EC2 instanceasked 2 years ago
Issue with linking an instance name with a dot (like aws.com) to s3 errorasked a year ago
Peering connection with ansible: "No route to host"asked 5 months ago
Unable to connect to remote host: No route to hostasked 2 months ago
"no route to host" instance id i-0a0d3444fd0a171feasked 2 years ago
EC2 Instance stuck in stopping stateasked a year ago
Unable to connect to EC2 instance in private Subnetasked a year ago
Connect Lightsail instance to AWS instance in a private subnetasked 5 months ago