<?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] - Auto scaling groups and logging in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/126069#M1390</link>
    <description>&lt;P&gt;Our environment:&lt;/P&gt;&lt;P&gt;MDS - R81 JHT23&lt;BR /&gt;Dedicated MLM/CLM - R81 JHT23&lt;BR /&gt;Cloudguard Gateways in AWS - R80.40 / Autoscaling / GWLB&lt;/P&gt;&lt;P&gt;I have observed that when AWS provisions a gateway, the CME does all of its work beautifully.&amp;nbsp; It brings the gateway into the respective CMA, provisions it and brings it into production.&amp;nbsp; And we're using auto-configuration scripts to setup all the base configuration stuff (passwords, snmp, ntp, so-on-and-so-forth).&amp;nbsp; It all works great!&lt;/P&gt;&lt;P&gt;But.&amp;nbsp; The CME appears to miss one step - installing database after the new gateways are online.&lt;/P&gt;&lt;P&gt;When a new gateway comes on line, it seems to be logging that data to the correct CLM.&amp;nbsp; But any searches on the logs for traffic a given AWS gateway is transiting returns nothing until I do a manual database install.&amp;nbsp; I tried using specific source/destination IP's and even using the origin of the gateway in question to do searches.&amp;nbsp; Nadda until the database is installed.&amp;nbsp; Then it works great.&lt;/P&gt;&lt;P&gt;Any chance that can get investigated?&amp;nbsp; Please?&amp;nbsp; With a side of Direct Connect on top?&lt;/P&gt;&lt;P&gt;In my happy little world, that's something the CME process should take care of.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 09 Aug 2021 15:20:18 GMT</pubDate>
    <dc:creator>Tommy_Forrest</dc:creator>
    <dc:date>2021-08-09T15:20:18Z</dc:date>
    <item>
      <title>[AWS] - Auto scaling groups and logging</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/126069#M1390</link>
      <description>&lt;P&gt;Our environment:&lt;/P&gt;&lt;P&gt;MDS - R81 JHT23&lt;BR /&gt;Dedicated MLM/CLM - R81 JHT23&lt;BR /&gt;Cloudguard Gateways in AWS - R80.40 / Autoscaling / GWLB&lt;/P&gt;&lt;P&gt;I have observed that when AWS provisions a gateway, the CME does all of its work beautifully.&amp;nbsp; It brings the gateway into the respective CMA, provisions it and brings it into production.&amp;nbsp; And we're using auto-configuration scripts to setup all the base configuration stuff (passwords, snmp, ntp, so-on-and-so-forth).&amp;nbsp; It all works great!&lt;/P&gt;&lt;P&gt;But.&amp;nbsp; The CME appears to miss one step - installing database after the new gateways are online.&lt;/P&gt;&lt;P&gt;When a new gateway comes on line, it seems to be logging that data to the correct CLM.&amp;nbsp; But any searches on the logs for traffic a given AWS gateway is transiting returns nothing until I do a manual database install.&amp;nbsp; I tried using specific source/destination IP's and even using the origin of the gateway in question to do searches.&amp;nbsp; Nadda until the database is installed.&amp;nbsp; Then it works great.&lt;/P&gt;&lt;P&gt;Any chance that can get investigated?&amp;nbsp; Please?&amp;nbsp; With a side of Direct Connect on top?&lt;/P&gt;&lt;P&gt;In my happy little world, that's something the CME process should take care of.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 15:20:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/126069#M1390</guid>
      <dc:creator>Tommy_Forrest</dc:creator>
      <dc:date>2021-08-09T15:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: [AWS] - Auto scaling groups and logging</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/126087#M1391</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/10886"&gt;@Tommy_Forrest&lt;/a&gt;,&lt;BR /&gt;Described configuration should work without installing DB&lt;BR /&gt;Do you have a SR opened for this issue?&lt;BR /&gt;If not I suggest to open SR and share it with me over private massage&lt;BR /&gt;In the SR please attach logs gathered by the CME Log Collector (see &lt;A href="https://sc1.checkpoint.com/documents/IaaS/WebAdminGuides/EN/CP_CME/Default.htm?cshid=ID011" target="_blank" rel="noopener"&gt;https://sc1.checkpoint.com/documents/IaaS/WebAdminGuides/EN/CP_CME/Default.htm?cshid=ID011&lt;/A&gt; (This link was edited by Check Point on 19 Dec 2021))&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Roman&lt;/P&gt;</description>
      <pubDate>Sun, 19 Dec 2021 13:08:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/126087#M1391</guid>
      <dc:creator>Roman_Kats</dc:creator>
      <dc:date>2021-12-19T13:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: [AWS] - Auto scaling groups and logging</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/128161#M1392</link>
      <description>&lt;P&gt;Updating this thread in case anyone finds this in a web search - R&amp;amp;D did discover that install database wasn't getting done and they're looking into fixing CME to address this issue in a future release.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Aug 2021 18:37:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/AWS-Auto-scaling-groups-and-logging/m-p/128161#M1392</guid>
      <dc:creator>Tommy_Forrest</dc:creator>
      <dc:date>2021-08-26T18:37:46Z</dc:date>
    </item>
  </channel>
</rss>

