<?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: AWS / Multiple subnets across multiple AZs - Multiple NICS? in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192127#M201</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/38823"&gt;@niyengar&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;In AWS the firewall needs to have an interface in the&amp;nbsp;subnet for&amp;nbsp;it&amp;nbsp;to be able to see the traffic.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other solution is to use a Transit VPC. This will be a centralized VPC with firewalls and then other VPCS with variouis APPS connect to this VPC to send data out (outbound protection) and you can also achieve inter-VPC security.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working on a &amp;nbsp;fully automated solution and it should be relased in the next few weeks.&lt;/P&gt;&lt;P&gt;@You can contact your SE and have them setup a meeting with folks here &amp;nbsp;@ paloalto networks and we'll be happy to give you an overview.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Great... sounds intriguing.&amp;nbsp; I submitted a request online but haven't heard.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there an easier way to identify the SE that would handle our account?&lt;/P&gt;</description>
    <pubDate>Mon, 18 Dec 2017 19:59:17 GMT</pubDate>
    <dc:creator>spetty01</dc:creator>
    <dc:date>2017-12-18T19:59:17Z</dc:date>
    <item>
      <title>AWS / Multiple subnets across multiple AZs - Multiple NICS?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192110#M199</link>
      <description>&lt;P&gt;Very new to VM-300 and PA, deploying it in AWS with 2 availability zones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We'd like to have 3 private subnets in each AZ - DMZ, application, and data, as well as a public subnet for the EIP interface.&amp;nbsp; Ideally all traffic between subnets would flow through the VM-300, but this doesn't seem possible to us without multiple NICs, one per subnet.&amp;nbsp; Is that accurate?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to understand what best practices are with this architecture.&amp;nbsp; Should we simply call public untrust and everything else trusted, and then just have one NIC in each, or is there a way that we can have all traffic between the subnets, or at least between the DMZ and others transit the VM-300?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The limitation of course on NICs is cost - the instances with 8 network interfaces are prohibitively expensive for a firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestions would be appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2017 17:33:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192110#M199</guid>
      <dc:creator>spetty01</dc:creator>
      <dc:date>2017-12-18T17:33:33Z</dc:date>
    </item>
    <item>
      <title>Re: AWS / Multiple subnets across multiple AZs - Multiple NICS?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192118#M200</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;In AWS the firewall needs to have an interface in the&amp;nbsp;subnet for&amp;nbsp;it&amp;nbsp;to be able to see the traffic.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other solution is to use a Transit VPC. This will be a centralized VPC with firewalls and then other VPCS with variouis APPS connect to this VPC to send data out (outbound protection) and you can also achieve inter-VPC security.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working on a &amp;nbsp;fully automated solution and it should be relased in the next few weeks.&lt;/P&gt;&lt;P&gt;You can contact your SE and have them setup a meeting with folks here &amp;nbsp;@ paloalto networks and we'll be happy to give you an overview.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2017 19:02:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192118#M200</guid>
      <dc:creator>niyengar</dc:creator>
      <dc:date>2017-12-18T19:02:45Z</dc:date>
    </item>
    <item>
      <title>Re: AWS / Multiple subnets across multiple AZs - Multiple NICS?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192127#M201</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/38823"&gt;@niyengar&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;In AWS the firewall needs to have an interface in the&amp;nbsp;subnet for&amp;nbsp;it&amp;nbsp;to be able to see the traffic.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other solution is to use a Transit VPC. This will be a centralized VPC with firewalls and then other VPCS with variouis APPS connect to this VPC to send data out (outbound protection) and you can also achieve inter-VPC security.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working on a &amp;nbsp;fully automated solution and it should be relased in the next few weeks.&lt;/P&gt;&lt;P&gt;@You can contact your SE and have them setup a meeting with folks here &amp;nbsp;@ paloalto networks and we'll be happy to give you an overview.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Great... sounds intriguing.&amp;nbsp; I submitted a request online but haven't heard.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there an easier way to identify the SE that would handle our account?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2017 19:59:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192127#M201</guid>
      <dc:creator>spetty01</dc:creator>
      <dc:date>2017-12-18T19:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: AWS / Multiple subnets across multiple AZs - Multiple NICS?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192147#M204</link>
      <description>&lt;P&gt;What company do you represent?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you don't want to advertise here, you can&amp;nbsp;unicast me at niyengar[at]paloaltonetworks[dot]com&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2017 21:47:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-multiple-subnets-across-multiple-azs-multiple-nics/m-p/192147#M204</guid>
      <dc:creator>niyengar</dc:creator>
      <dc:date>2017-12-18T21:47:03Z</dc:date>
    </item>
  </channel>
</rss>

