Reach third-party resources in an aws account that only provides a vpc peer connection from our data center.

Hello @Unique,

It's crucial to be mindful of the limitations that come with **VPC Peering **when endeavoring to access resources beyond the peered VPC. Here's a rundown of key considerations when having Peering between VPCA and VPCB:

• If VPC A has an internet gateway, resources in VPC B won't be able to utilize it to gain access to the internet.
• Should VPC A rely on a NAT device for internet access within its subnets, resources in VPC B won't have access through this NAT device.
• Any VPN connection between VPC A and a corporate network won't be accessible for resources in VPC B to communicate with the corporate network.
• Similarly, if VPC A has an AWS Direct Connect connection to a corporate network, resources in VPC B won't be able to use it for communication.
• If VPC A has a gateway endpoint specifically configured for private subnets to access Amazon S3, resources in VPC B won't be able to leverage it for Amazon S3 access.

In view of these limitations, you may want to consider implementing a **Proxy Server **within your account's VPC. This can change the source IP address, making the traffic appear as if it's initiated from your local VPC. Alternatively, you could explore replacing VPC Peering with a **Transit Gateway **for a more flexible and efficient network communication.

Best regards.