<?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 Multi-AZ HA Palo deployment with three zones in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multi-az-ha-palo-deployment-with-three-zones/m-p/243948#M486</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm looking for any walkthroughs using lambda functions to move the EIP between Palo's in two Availability Zones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My assumption would be EIPs in two subnets for each of the three zones. How to accomplish access to Prod and DMZ:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;S2S VPN connections to the Palos to prod and DMZ.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;ELB endpoints to Prod and DMZ.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For public IP address, I assume the use Lambda moving the Public EIP between ENIs for S2S VPNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is what I envision this would look like:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Palo Alto HA in AWS.JPG" style="width: 520px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/17999iA247E01326146CE2/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Palo Alto HA in AWS.JPG" alt="Palo Alto HA in AWS.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd appreciate&amp;nbsp;any a walkthrough or video I could follow if anyone has it. I think I have a handle on this, but if I don't please let me know.&amp;nbsp; I'd rather have something to go by than to have to figure all this out myself.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Dec 2018 22:25:33 GMT</pubDate>
    <dc:creator>Coveny</dc:creator>
    <dc:date>2018-12-19T22:25:33Z</dc:date>
    <item>
      <title>AWS Multi-AZ HA Palo deployment with three zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multi-az-ha-palo-deployment-with-three-zones/m-p/243948#M486</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm looking for any walkthroughs using lambda functions to move the EIP between Palo's in two Availability Zones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My assumption would be EIPs in two subnets for each of the three zones. How to accomplish access to Prod and DMZ:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;S2S VPN connections to the Palos to prod and DMZ.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;ELB endpoints to Prod and DMZ.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For public IP address, I assume the use Lambda moving the Public EIP between ENIs for S2S VPNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is what I envision this would look like:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Palo Alto HA in AWS.JPG" style="width: 520px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/17999iA247E01326146CE2/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Palo Alto HA in AWS.JPG" alt="Palo Alto HA in AWS.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd appreciate&amp;nbsp;any a walkthrough or video I could follow if anyone has it. I think I have a handle on this, but if I don't please let me know.&amp;nbsp; I'd rather have something to go by than to have to figure all this out myself.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 22:25:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multi-az-ha-palo-deployment-with-three-zones/m-p/243948#M486</guid>
      <dc:creator>Coveny</dc:creator>
      <dc:date>2018-12-19T22:25:33Z</dc:date>
    </item>
  </channel>
</rss>

