<?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 Re: Autoscale (manually created VM-SERIES) on AWS in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280420#M646</link>
    <description>&lt;P&gt;That would vary based on your environment and the type of traffic you inspect. You may want to look at a sample size of your data to find the value better suited for your app mix. For example,&amp;nbsp; if you have high session count traffic then you may want to trigger based on session utilization table. If you have traffic that depleted dataplane cpu then you may want to look at the processor utilization. It all depends on the type of traffic you have. Our Auto Scale templates support this and you can set your ASG to have 2 FW by default. But if manually scale is what you want you will have to manually monitor this or write a script to check either metric.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2019 23:54:30 GMT</pubDate>
    <dc:creator>jperry1</dc:creator>
    <dc:date>2019-07-31T23:54:30Z</dc:date>
    <item>
      <title>Autoscale (manually created VM-SERIES) on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280337#M645</link>
      <description>&lt;P&gt;two firewalls behind an NLB.&amp;nbsp;&lt;/P&gt;&lt;P&gt;what approach would you take to spin up additional firewalls if a certain threshold is hit (what threshold would you trigger on)?&amp;nbsp;&lt;/P&gt;&lt;P&gt;i've looked at the templates provided by palo alto but this would be adding additional firewalls in already established VPCs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;also use panorama&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 15:56:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280337#M645</guid>
      <dc:creator>Cdchamberlin</dc:creator>
      <dc:date>2019-07-31T15:56:30Z</dc:date>
    </item>
    <item>
      <title>Re: Autoscale (manually created VM-SERIES) on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280420#M646</link>
      <description>&lt;P&gt;That would vary based on your environment and the type of traffic you inspect. You may want to look at a sample size of your data to find the value better suited for your app mix. For example,&amp;nbsp; if you have high session count traffic then you may want to trigger based on session utilization table. If you have traffic that depleted dataplane cpu then you may want to look at the processor utilization. It all depends on the type of traffic you have. Our Auto Scale templates support this and you can set your ASG to have 2 FW by default. But if manually scale is what you want you will have to manually monitor this or write a script to check either metric.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 23:54:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280420#M646</guid>
      <dc:creator>jperry1</dc:creator>
      <dc:date>2019-07-31T23:54:30Z</dc:date>
    </item>
    <item>
      <title>Re: Autoscale (manually created VM-SERIES) on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280609#M647</link>
      <description>&lt;P&gt;Also, for AWS auto scale 2.1, it supports deployment into an existing application environment.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/auto-scale-vm-series-firewalls-with-the-amazon-elb/vm-series-auto-scale-template-for-aws-version-v21.html#ide07a7726-45c0-414e-98c5-33c5034f5d64" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-0/vm-series-deployment/set-up-the-vm-series-firewall-on-aws/auto-scale-vm-series-firewalls-with-the-amazon-elb/vm-series-auto-scale-template-for-aws-version-v21.html#ide07a7726-45c0-414e-98c5-33c5034f5d64&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 18:50:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/autoscale-manually-created-vm-series-on-aws/m-p/280609#M647</guid>
      <dc:creator>jperry1</dc:creator>
      <dc:date>2019-08-01T18:50:20Z</dc:date>
    </item>
  </channel>
</rss>

