<?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 terraform support NGFW VM-Series in the HA pair in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/terraform-support-ngfw-vm-series-in-the-ha-pair/m-p/419173#M2723</link>
    <description>&lt;P&gt;With AWS ingress routing, the HA pair of ngfw-vm can be leverage to inspect all ingress and egress traffic without ELB to mess up ports/IPs, just like the old days of private datacenter.&amp;nbsp; See &lt;A href="https://aws.amazon.com/blogs/aws/new-vpc-ingress-routing-simplifying-integration-of-third-party-appliances/" target="_blank"&gt;https://aws.amazon.com/blogs/aws/new-vpc-ingress-routing-simplifying-integration-of-third-party-appliances/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However the terraform pan-os provider does not support HA pair config. Basically I have to find out which FW is active in the HA pair, otherwise the commit will fail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone has better idea how to use terraform to deal with active-passive HA pair? This option is really more attractive compared with any other solution with ELB!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suggestion and ideas please. Anyone is making decision for pan-os terraform provider, it would be great to add HA support for terraform!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 13 Jul 2021 22:42:10 GMT</pubDate>
    <dc:creator>JZhou4</dc:creator>
    <dc:date>2021-07-13T22:42:10Z</dc:date>
    <item>
      <title>terraform support NGFW VM-Series in the HA pair</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/terraform-support-ngfw-vm-series-in-the-ha-pair/m-p/419173#M2723</link>
      <description>&lt;P&gt;With AWS ingress routing, the HA pair of ngfw-vm can be leverage to inspect all ingress and egress traffic without ELB to mess up ports/IPs, just like the old days of private datacenter.&amp;nbsp; See &lt;A href="https://aws.amazon.com/blogs/aws/new-vpc-ingress-routing-simplifying-integration-of-third-party-appliances/" target="_blank"&gt;https://aws.amazon.com/blogs/aws/new-vpc-ingress-routing-simplifying-integration-of-third-party-appliances/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However the terraform pan-os provider does not support HA pair config. Basically I have to find out which FW is active in the HA pair, otherwise the commit will fail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone has better idea how to use terraform to deal with active-passive HA pair? This option is really more attractive compared with any other solution with ELB!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suggestion and ideas please. Anyone is making decision for pan-os terraform provider, it would be great to add HA support for terraform!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jul 2021 22:42:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/terraform-support-ngfw-vm-series-in-the-ha-pair/m-p/419173#M2723</guid>
      <dc:creator>JZhou4</dc:creator>
      <dc:date>2021-07-13T22:42:10Z</dc:date>
    </item>
  </channel>
</rss>

