<?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 - Availability Zones - Palo Alto Location in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones-palo-alto-location/m-p/283485#M656</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking at deploying the VM-Series into AWS to replace an existing deployment of Sophos UTMs. But can someone help tell me if I am going mad, or have found a limiation. The VM-Series would be used for egress traffic only, and we dont have tight SLA's so ideally a single VM FW will sort us out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I deploy a single VM-Series into say Availability Zone-1B, and some other hosts are also in the same AZ, now I can route all my traffic to the VM-Series FW and egress out to the web. All happy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I do the same have a VM-Series in 1B, but have some clients in AZ-1C, they cannot route out to the internet. I can see the traffic is hitting the firewall on the Monitor tab of the Firewall, but that is about as far as it gets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there some horrible limitation where these firewalls can only route traffic if they are in the same AZ as the client?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the Sophos UTM this has never been an issue before, whatever you point at it from whatever location it will just route out to the web.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course could be I am doing something really stupid as well &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 19 Aug 2019 10:30:01 GMT</pubDate>
    <dc:creator>steviehyperb</dc:creator>
    <dc:date>2019-08-19T10:30:01Z</dc:date>
    <item>
      <title>AWS - Availability Zones - Palo Alto Location</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones-palo-alto-location/m-p/283485#M656</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking at deploying the VM-Series into AWS to replace an existing deployment of Sophos UTMs. But can someone help tell me if I am going mad, or have found a limiation. The VM-Series would be used for egress traffic only, and we dont have tight SLA's so ideally a single VM FW will sort us out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I deploy a single VM-Series into say Availability Zone-1B, and some other hosts are also in the same AZ, now I can route all my traffic to the VM-Series FW and egress out to the web. All happy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I do the same have a VM-Series in 1B, but have some clients in AZ-1C, they cannot route out to the internet. I can see the traffic is hitting the firewall on the Monitor tab of the Firewall, but that is about as far as it gets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there some horrible limitation where these firewalls can only route traffic if they are in the same AZ as the client?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the Sophos UTM this has never been an issue before, whatever you point at it from whatever location it will just route out to the web.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course could be I am doing something really stupid as well &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2019 10:30:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones-palo-alto-location/m-p/283485#M656</guid>
      <dc:creator>steviehyperb</dc:creator>
      <dc:date>2019-08-19T10:30:01Z</dc:date>
    </item>
  </channel>
</rss>

