Palo Alto VM Series Routing Problem in AWS

CLombardi — Wed, 08 Jan 2025 23:19:05 GMT

I am working on a greenfield proof of concept and I am running into some challenges. I am trying to get VPC A in Account A to route internet traffic through VPC B in Account B using VPC peering. The Palo Alto VM Series resides in VPC B. Is this configuration possible, or am I forced to use a Transit Gateway or IPSEC VPN?

Account A / VPC A CIDR 10.0.1.32/27

Account B / VPC B CIDR 10.0.0.0/24

Peering connection is active
Source / Destination check disabled on all interfaces.

Account A / VPC A Peering:
0.0.0.0/0 => <peering connection>
10.0.1.32/27 => local

Account B / VPC B Route Table (Main Route Table associated with the subnet for the Trust interface):
0.0.0.0/0 => <untrust interface>
10.0.1.32/27 => <peering connection>

Account B / VPC B Route Table (Untrust Interface)

0.0.0.0/0 => <internet gateway>

10.0.1.32/27 => <peering connection>

Re: Palo Alto VM Series Routing Problem in AWS

Murph — Mon, 27 Jan 2025 17:02:22 GMT

Curious have you considered using AWS Privatelink?

topic Palo Alto VM Series Routing Problem in AWS in VM-Series in the Public Cloud

Palo Alto VM Series Routing Problem in AWS

Re: Palo Alto VM Series Routing Problem in AWS