Boundary not able to resolve AWS EC2 private IP hosted in a different AWS account


I have a working Boundary setup in an AWS account and trying to connect an ec2 instance’s private IP hosted in a different AWS account (Both AWS accounts are VPC peered.) Boundary is not able to resolve and locate the target instance and connection timed out.

When I connect using public ip of the same ec2 instance, Boundary is able to resolve and connect to the instance using provided credentials .

Can you SSH to one of the target instances from another instance in the peered VPC where Boundary is? What are the CIDRs of each VPC set to?

@omkensey We use terraform and somehow the CIDR block of the peer VPC to the VPC peering connection got removed . I have added it now and SSH is working via Boundary. Thanks for your support.

1 Like