<?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 Cross region ingress packet inspection with Palo Alto GWLB and TGW in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/cross-region-ingress-packet-inspection-with-palo-alto-gwlb-and/m-p/449247#M1391</link>
    <description>&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Currently doing POC and deployed a&amp;nbsp;&amp;nbsp;VM-Series with AWS Gateway Load Balancer/TGW mentioned &lt;A href="https://github.com/PaloAltoNetworks/AWS-GWLB-VMSeries/tree/main/terraform" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I was able to inspect the traffic inbound traffic as my security vpc (TGW/GWLB/VMSeries)a nd Spokes VPC (Application) is in the same region. Any idea how can I route my traffic for inbound inspection if my spokes VPC is different region than security VPC since gateway loablancer endpoint&amp;nbsp; is a regional service? I was able to route/inspect East-West and Outbound (to internet) using cross region transit gateway attachment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this diagram both security vpc and application vpc are in the same region, we were able to route the traffic for public subnet to pur firewall through gwlb endpoint. This is not possible if your spokes VPC is in a different region and VPC endpoint is a regional service, just like TGW.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/755a271cf78f756f01387001aa31e7807f41df51/68747470733a2f2f6769746875622e636f6d2f50616c6f416c746f4e6574776f726b732f4157532d47574c422d564d5365726965732f7261772f6d61696e2f7465727261666f726d2f746f706f6c6f67792e706e67" border="0" /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Nov 2021 15:54:36 GMT</pubDate>
    <dc:creator>ali_h3n</dc:creator>
    <dc:date>2021-11-24T15:54:36Z</dc:date>
    <item>
      <title>Cross region ingress packet inspection with Palo Alto GWLB and TGW</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/cross-region-ingress-packet-inspection-with-palo-alto-gwlb-and/m-p/449247#M1391</link>
      <description>&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Currently doing POC and deployed a&amp;nbsp;&amp;nbsp;VM-Series with AWS Gateway Load Balancer/TGW mentioned &lt;A href="https://github.com/PaloAltoNetworks/AWS-GWLB-VMSeries/tree/main/terraform" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I was able to inspect the traffic inbound traffic as my security vpc (TGW/GWLB/VMSeries)a nd Spokes VPC (Application) is in the same region. Any idea how can I route my traffic for inbound inspection if my spokes VPC is different region than security VPC since gateway loablancer endpoint&amp;nbsp; is a regional service? I was able to route/inspect East-West and Outbound (to internet) using cross region transit gateway attachment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this diagram both security vpc and application vpc are in the same region, we were able to route the traffic for public subnet to pur firewall through gwlb endpoint. This is not possible if your spokes VPC is in a different region and VPC endpoint is a regional service, just like TGW.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/755a271cf78f756f01387001aa31e7807f41df51/68747470733a2f2f6769746875622e636f6d2f50616c6f416c746f4e6574776f726b732f4157532d47574c422d564d5365726965732f7261772f6d61696e2f7465727261666f726d2f746f706f6c6f67792e706e67" border="0" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 15:54:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/cross-region-ingress-packet-inspection-with-palo-alto-gwlb-and/m-p/449247#M1391</guid>
      <dc:creator>ali_h3n</dc:creator>
      <dc:date>2021-11-24T15:54:36Z</dc:date>
    </item>
  </channel>
</rss>

