<?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 AWS GWLB with secondary appliance in chain in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-gwlb-with-secondary-appliance-in-chain/m-p/1235471#M2384</link>
    <description>&lt;P&gt;I'm working with a dedicated inspection VPC+GWLB for the first time. I have the TGW, GWLB, and general routing working with just the Palo in play. East west traffic from vpc1 to vpc2 is correctly going into the inspection VPC and I can see the traffic in the Palo logs, etc...&lt;BR /&gt;&lt;BR /&gt;My question is: we want to add a second device in the chain. On prem we would have these inline, and traffic would flow in one interface of the palo, out the other to the other device, and out the other device on its way to destination.&lt;BR /&gt;&lt;BR /&gt;In our dedicated VPC, this isn't the case, the palo is a router-on-a-stick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My thought was to add a second interface that lives in the same subnet as the 2nd device, and use PBF to say that all traffic coming in on data interface 1 goes out interface 2 to the 2nd device. It would then come back on interface 2 and be returned to out interface 1 back to the GWLB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a feasible solution? is there another standard or best-practice method of chaining a second service behind the palo in a setup like this?&lt;/P&gt;</description>
    <pubDate>Tue, 05 Aug 2025 17:25:49 GMT</pubDate>
    <dc:creator>scotto</dc:creator>
    <dc:date>2025-08-05T17:25:49Z</dc:date>
    <item>
      <title>AWS GWLB with secondary appliance in chain</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-gwlb-with-secondary-appliance-in-chain/m-p/1235471#M2384</link>
      <description>&lt;P&gt;I'm working with a dedicated inspection VPC+GWLB for the first time. I have the TGW, GWLB, and general routing working with just the Palo in play. East west traffic from vpc1 to vpc2 is correctly going into the inspection VPC and I can see the traffic in the Palo logs, etc...&lt;BR /&gt;&lt;BR /&gt;My question is: we want to add a second device in the chain. On prem we would have these inline, and traffic would flow in one interface of the palo, out the other to the other device, and out the other device on its way to destination.&lt;BR /&gt;&lt;BR /&gt;In our dedicated VPC, this isn't the case, the palo is a router-on-a-stick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My thought was to add a second interface that lives in the same subnet as the 2nd device, and use PBF to say that all traffic coming in on data interface 1 goes out interface 2 to the 2nd device. It would then come back on interface 2 and be returned to out interface 1 back to the GWLB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a feasible solution? is there another standard or best-practice method of chaining a second service behind the palo in a setup like this?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 17:25:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-gwlb-with-secondary-appliance-in-chain/m-p/1235471#M2384</guid>
      <dc:creator>scotto</dc:creator>
      <dc:date>2025-08-05T17:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: AWS GWLB with secondary appliance in chain</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-gwlb-with-secondary-appliance-in-chain/m-p/1237699#M2390</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1497760599"&gt;@scotto&lt;/a&gt;&amp;nbsp;what is your final design?&amp;nbsp;We have designed and implemented one of the requirements with one GWLB endpoint for inbound and other GWLB endpoint for outbound with one interface for both in/out.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Sep 2025 06:22:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-gwlb-with-secondary-appliance-in-chain/m-p/1237699#M2390</guid>
      <dc:creator>skchakraborty</dc:creator>
      <dc:date>2025-09-11T06:22:29Z</dc:date>
    </item>
  </channel>
</rss>

