Score:0

AWS Peering connection with ansible: "No route to host"

es flag

I have an EC2 instance in us-east-1 which would like to communicate with another instance in us-west-2.

VPC-East CIDR: 172.16.0.0/16

VPC-West CIDR: 172.17.0.0/16

The used subnets in these VPCs are 172.(16 or 17).0.0/24 correspondingly.

I've created a Peering Connection between the two regions VPC and maybe it would help so I allowed:

  • Allow accepter VPC to resolve DNS of hosts in requester VPC to private IP addresses

  • Allow requester VPC to resolve DNS of hosts in accepter VPC to private IP addresses

I also added a new route at the route tables:

  • the other one's CIDR should be searched at the Peering Connection. I.e. at VPC-East:

enter image description here

I've created a Reachability Analyzer from the East instance to the Peering Connection and it succeeds.

But ansible still fails to connect from East to West (From East to East it worked earlier).

Failed to connect to the host via ssh: ssh: connect to host 172.17.0.129 port 22: No route to host

Maybe it's not related to my main problem, but:

  • Another instance in the west can be accessed via a public IP by me and by East instance.
  • But it show this: Instance reachability check failed
  • While I can SSH, access the website it hosts, etc.

Thanks in advance!

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.