<?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 Load Balancer Sandwich Outbound Traffic in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-load-balancer-sandwich-outbound-traffic/m-p/223076#M370</link>
    <description>&lt;P&gt;&lt;SPAN&gt;With the jumpbox, you have to ensure it that it is in the NATGateway subnet, that is the only subnet that has an IGW for the EIPs to utilize.&amp;nbsp; Additionally, there is a security group created by the template that allows ports 22/3389 for access to the jumpbox.&amp;nbsp; If that SG was not used for the jumpbox, ensure that your jumpbox does have the proper SG applied.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As for outbound, this template was not&amp;nbsp;designed&amp;nbsp;for protection of traffic originating within the VPC.&amp;nbsp; You can choose to create a route for your application servers pointing to the Trust side of the firewall in the corresponding AZ and validate that ETH2 has Source/Destination check disabled.&amp;nbsp; You will then need to add corresponding security and hide nat policies to allow the traffic.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please note that this creates a single point of failure within the VPC.&amp;nbsp; In order to perform outbound inspection of traffic originating from within the VPC, utilization of a transit VPC or other automation to monitor the firewalls and move the routes is necessary.&amp;nbsp; That is topic better suited for a discussion with your Palo Alto Networks SE.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Jul 2018 12:26:30 GMT</pubDate>
    <dc:creator>jmeurer</dc:creator>
    <dc:date>2018-07-20T12:26:30Z</dc:date>
    <item>
      <title>AWS Load Balancer Sandwich Outbound Traffic</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-load-balancer-sandwich-outbound-traffic/m-p/222805#M369</link>
      <description>&lt;P&gt;We have been trying to get the load balancer sandwich (&lt;A href="https://github.com/PaloAltoNetworks/aws-alb-sandwich" target="_blank"&gt;https://github.com/PaloAltoNetworks/aws-alb-sandwich&lt;/A&gt;) working but have had little success. Has anyone been successful?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First of all, we can't figure out how to send outbound traffic through the firewalls. An internal, outbound-facing load balancer should do the trick, but it seems a requirement to configured each TCP port needed for Internet connectivity. Is there another way to get this done?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After we (finally, after several tries) got a CF stack to complete successfully, we could never connect to our jump box. We would rather put an elastic IP on the MGMT interfaces and get the firewalls configured - then configured access through the firewalls to the jump box. We couldn't get into either the firewalls or jump box - connections just timed out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for any suggestions.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 18:21:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-load-balancer-sandwich-outbound-traffic/m-p/222805#M369</guid>
      <dc:creator>JakeRocus</dc:creator>
      <dc:date>2018-07-18T18:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: AWS Load Balancer Sandwich Outbound Traffic</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-load-balancer-sandwich-outbound-traffic/m-p/223076#M370</link>
      <description>&lt;P&gt;&lt;SPAN&gt;With the jumpbox, you have to ensure it that it is in the NATGateway subnet, that is the only subnet that has an IGW for the EIPs to utilize.&amp;nbsp; Additionally, there is a security group created by the template that allows ports 22/3389 for access to the jumpbox.&amp;nbsp; If that SG was not used for the jumpbox, ensure that your jumpbox does have the proper SG applied.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As for outbound, this template was not&amp;nbsp;designed&amp;nbsp;for protection of traffic originating within the VPC.&amp;nbsp; You can choose to create a route for your application servers pointing to the Trust side of the firewall in the corresponding AZ and validate that ETH2 has Source/Destination check disabled.&amp;nbsp; You will then need to add corresponding security and hide nat policies to allow the traffic.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please note that this creates a single point of failure within the VPC.&amp;nbsp; In order to perform outbound inspection of traffic originating from within the VPC, utilization of a transit VPC or other automation to monitor the firewalls and move the routes is necessary.&amp;nbsp; That is topic better suited for a discussion with your Palo Alto Networks SE.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jul 2018 12:26:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-load-balancer-sandwich-outbound-traffic/m-p/223076#M370</guid>
      <dc:creator>jmeurer</dc:creator>
      <dc:date>2018-07-20T12:26:30Z</dc:date>
    </item>
  </channel>
</rss>

