<?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 Cloudguard  AWS TCP Health probing in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/Cloudguard-AWS-TCP-Health-probing/m-p/72823#M2654</link>
    <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;I have deployed cloudguard auto scaling in AWS; I simply followed AWS-Checkpoint document.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;So there's zero touch configuration has been achieved thru tagging the autoprovision template value, automatcially NAT and access polices created in the firewall. Thru which&amp;nbsp;&amp;nbsp;I migrated some applications up and running fine. All the Ext. and Int. LBs are (application-type) and listeners 443.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Here now, I created a network type lb health probing getting failed for one of a firewall. However I could see the SYN in the firewall, corresponding access/NAT rule in placed. But still failing at firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jan 2020 09:47:40 GMT</pubDate>
    <dc:creator>ramakrishnan</dc:creator>
    <dc:date>2020-01-21T09:47:40Z</dc:date>
    <item>
      <title>Cloudguard  AWS TCP Health probing</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Cloudguard-AWS-TCP-Health-probing/m-p/72823#M2654</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;I have deployed cloudguard auto scaling in AWS; I simply followed AWS-Checkpoint document.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;So there's zero touch configuration has been achieved thru tagging the autoprovision template value, automatcially NAT and access polices created in the firewall. Thru which&amp;nbsp;&amp;nbsp;I migrated some applications up and running fine. All the Ext. and Int. LBs are (application-type) and listeners 443.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Here now, I created a network type lb health probing getting failed for one of a firewall. However I could see the SYN in the firewall, corresponding access/NAT rule in placed. But still failing at firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2020 09:47:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Cloudguard-AWS-TCP-Health-probing/m-p/72823#M2654</guid>
      <dc:creator>ramakrishnan</dc:creator>
      <dc:date>2020-01-21T09:47:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudguard  AWS TCP Health probing</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Cloudguard-AWS-TCP-Health-probing/m-p/72932#M2655</link>
      <description>If you click on the log entry and pull up the log card, what do you see?</description>
      <pubDate>Wed, 22 Jan 2020 01:50:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Cloudguard-AWS-TCP-Health-probing/m-p/72932#M2655</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-01-22T01:50:02Z</dc:date>
    </item>
  </channel>
</rss>

