<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: GWLB and Palo Alto Zones in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396120#M1148</link>
    <description>&lt;P&gt;The zoning capabilities is dependant on the traffic direction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Inbound, we have the ability to map GWLBe's from the various inbound VPCs to a subInterface.&amp;nbsp; This traffic will still be Intrazone, but you can have each VPC in its own zone.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/associate-a-vpc-endpoint-with-a-vm-series-interface.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/associate-a-vpc-endpoint-with-a-vm-series-interface.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Outbound, we added the ability to route traffic outbound out of an Untrust interface using Overlay routing in 10.0.5.&amp;nbsp; This allows for the creation of the traditional Trust-&amp;gt;Untrust style policy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/enable-overlay-routing-for-the-vm-series-on-aws.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/enable-overlay-routing-for-the-vm-series-on-aws.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;East-West, VPC to VPC communication through a TGW deployment cannot be broken into zones.&amp;nbsp; This traffic must hairpin back to the GWLB for routing.&amp;nbsp; This traffic will continue to be Intrazone and your policies will need to be DAG or Subnet based.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Apr 2021 20:09:38 GMT</pubDate>
    <dc:creator>jmeurer</dc:creator>
    <dc:date>2021-04-06T20:09:38Z</dc:date>
    <item>
      <title>GWLB and Palo Alto Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396111#M1147</link>
      <description>&lt;P&gt;I am building some PA VM's behind GWLB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i would like to do traffic between VPC's to flow through this GWLB and TGW which appears to be possible however i can not find any documentation on how to seperate these into different Zones within the palo. I would like the Traffic from VPC A and VPC B to be mapped to different Palo Alto Zones. I was told this is possible but can't find any reference.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 19:57:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396111#M1147</guid>
      <dc:creator>jon.swick</dc:creator>
      <dc:date>2021-04-06T19:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: GWLB and Palo Alto Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396120#M1148</link>
      <description>&lt;P&gt;The zoning capabilities is dependant on the traffic direction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Inbound, we have the ability to map GWLBe's from the various inbound VPCs to a subInterface.&amp;nbsp; This traffic will still be Intrazone, but you can have each VPC in its own zone.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/associate-a-vpc-endpoint-with-a-vm-series-interface.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/associate-a-vpc-endpoint-with-a-vm-series-interface.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Outbound, we added the ability to route traffic outbound out of an Untrust interface using Overlay routing in 10.0.5.&amp;nbsp; This allows for the creation of the traditional Trust-&amp;gt;Untrust style policy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/enable-overlay-routing-for-the-vm-series-on-aws.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/vm-series-integration-with-gateway-load-balancer/integrate-the-vm-series-with-an-aws-gateway-load-balancer/enable-overlay-routing-for-the-vm-series-on-aws.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;East-West, VPC to VPC communication through a TGW deployment cannot be broken into zones.&amp;nbsp; This traffic must hairpin back to the GWLB for routing.&amp;nbsp; This traffic will continue to be Intrazone and your policies will need to be DAG or Subnet based.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 20:09:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396120#M1148</guid>
      <dc:creator>jmeurer</dc:creator>
      <dc:date>2021-04-06T20:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: GWLB and Palo Alto Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396128#M1149</link>
      <description>&lt;P&gt;Is there any reason to map the VPC's to zones for inbound then if i can't create zone based policies?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;are you stating that if VPC A is sending traffic to VPC B the palo will recognize the inbound as coming from Zone A but will send it out "Zone A" because it hairpins. so i just couldnt define destination zones but i could still utilize source zone?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 20:33:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396128#M1149</guid>
      <dc:creator>jon.swick</dc:creator>
      <dc:date>2021-04-06T20:33:30Z</dc:date>
    </item>
    <item>
      <title>Re: GWLB and Palo Alto Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396139#M1150</link>
      <description>&lt;P&gt;The purpose for the Zones in an inbound flow is to handle the possibility of overlapping IP schemes when not using TGW. &amp;nbsp;Diagrams for this flow are here. &amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-vm-series-gateway-load-balancers-not-working/m-p/373760#M1074" target="_blank"&gt;https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-vm-series-gateway-load-balancers-not-working/m-p/373760#M1074&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In VPC to VPC communication the traffic is as follows. &amp;nbsp;This traffic flow hairpins back to the GWLBe before routing back to the TGW. &amp;nbsp;This traffic must stay within the GENEVE encapsulation tunnel to maintain the 5-tuple perisistence that the GWLB performs.&lt;/P&gt;&lt;P&gt;VPCa -&amp;gt; TGW -&amp;gt; Firewall VPC -&amp;gt; GWLBe -&amp;gt; firewalls -&amp;gt; GWLBe -&amp;gt; tgw -&amp;gt; VPCb&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 21:32:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396139#M1150</guid>
      <dc:creator>jmeurer</dc:creator>
      <dc:date>2021-04-06T21:32:59Z</dc:date>
    </item>
    <item>
      <title>Re: GWLB and Palo Alto Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396140#M1151</link>
      <description>&lt;P&gt;Awesome!! Thank you so much for your help that put a light on a lot of things.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 21:38:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/gwlb-and-palo-alto-zones/m-p/396140#M1151</guid>
      <dc:creator>jon.swick</dc:creator>
      <dc:date>2021-04-06T21:38:59Z</dc:date>
    </item>
  </channel>
</rss>

