<?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 CloudTrail SQS Based S3 error in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/580148#M102363</link>
    <description>&lt;P&gt;Same issue for ALB access log collection using the SQS based S3 input after upgrading to 5.2.1.&amp;nbsp; Not only is this not indexing the S3 logs, but it's also deleting the SQS messages so it's not appropriately handling the error.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jan 2022 18:07:35 GMT</pubDate>
    <dc:creator>tlanghals_il</dc:creator>
    <dc:date>2022-01-06T18:07:35Z</dc:date>
    <item>
      <title>AWS CloudTrail SQS Based S3 error?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/579975#M102354</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I tried to configure CloudTrail SQS Based S3 and I got the following message:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN class=""&gt;Warning:&lt;/SPAN&gt; &lt;SPAN class=""&gt;This&lt;/SPAN&gt; &lt;SPAN class=""&gt;message&lt;/SPAN&gt; &lt;SPAN class=""&gt;does&lt;/SPAN&gt; &lt;SPAN class=""&gt;not&lt;/SPAN&gt; &lt;SPAN class=""&gt;have&lt;/SPAN&gt; &lt;SPAN class=""&gt;a&lt;/SPAN&gt; &lt;SPAN class=""&gt;valid&lt;/SPAN&gt; &lt;SPAN class=""&gt;SNS&lt;/SPAN&gt; &lt;SPAN class=""&gt;Signature&lt;/SPAN&gt; &lt;SPAN class=""&gt;None&lt;/SPAN&gt; &lt;SPAN class=""&gt;None&lt;/SPAN&gt; &lt;SPAN class=""&gt;doesn&lt;/SPAN&gt;&lt;SPAN&gt;'&lt;/SPAN&gt;&lt;SPAN class=""&gt;t&lt;/SPAN&gt; &lt;SPAN class=""&gt;match&lt;/SPAN&gt; &lt;SPAN class=""&gt;required&lt;/SPAN&gt; &lt;SPAN class=""&gt;format&lt;/SPAN&gt;&lt;SPAN&gt; '&lt;/SPAN&gt;&lt;SPAN class=""&gt;^&lt;A href="https://sns\" target="_blank" rel="noopener"&gt;https://sns\&lt;/A&gt;\.&lt;/SPAN&gt;&lt;SPAN&gt;[&lt;/SPAN&gt;&lt;SPAN class=""&gt;-a-z0-9&lt;/SPAN&gt;&lt;SPAN&gt;]+&lt;/SPAN&gt;&lt;SPAN class=""&gt;\\.amazonaws\\.com&lt;/SPAN&gt;&lt;SPAN&gt;(?&lt;/SPAN&gt;&lt;SPAN class=""&gt;:\\.cn&lt;/SPAN&gt;&lt;SPAN&gt;)?&lt;/SPAN&gt;&lt;SPAN class=""&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;'" &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Sometimes I also get:&lt;/P&gt;
&lt;P&gt;"Failed to delete message"&lt;/P&gt;
&lt;P&gt;I have no clue where to look in order to solve this issue. I will appreciate any help!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 16:03:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/579975#M102354</guid>
      <dc:creator>leuorrouel</dc:creator>
      <dc:date>2023-03-15T16:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/580148#M102363</link>
      <description>&lt;P&gt;Same issue for ALB access log collection using the SQS based S3 input after upgrading to 5.2.1.&amp;nbsp; Not only is this not indexing the S3 logs, but it's also deleting the SQS messages so it's not appropriately handling the error.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 18:07:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/580148#M102363</guid>
      <dc:creator>tlanghals_il</dc:creator>
      <dc:date>2022-01-06T18:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/580656#M102432</link>
      <description>&lt;P&gt;Having the same issues in the cloud.&amp;nbsp; Was upgraded to 5.2.1 last night and all inputs are doing the exact same thing.&lt;BR /&gt;&lt;BR /&gt;Pulling data from the Que,&amp;nbsp; warning, not indexing and the Que are cleared.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2022 17:13:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/580656#M102432</guid>
      <dc:creator>parcflyer</dc:creator>
      <dc:date>2022-01-11T17:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581548#M102516</link>
      <description>&lt;P&gt;Haven't looked into this too much, but I'm guessing it is related to the updates in version 5.2.1:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/AddOns/released/AWS/Releasenotes" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/AddOns/released/AWS/Releasenotes&lt;/A&gt;&lt;/P&gt;&lt;P&gt;"""&lt;/P&gt;&lt;P&gt;Version 5.2.1 of the Splunk Add-on for AWS version contains the following new and changed features:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;DIV class=""&gt;Added validation of the signature of the SNS message being sent from SQS queue to Splunk. The source of the logs is validated by matching the signature of the SNS message with the signature field.&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;"""&lt;/P&gt;&lt;P&gt;The setup docs for the CloudTrail input state S3-&amp;gt;SNS-&amp;gt;SQS now. I don't think this was the case before, but I don't have a copy of the old docs to check.&lt;/P&gt;&lt;P&gt;It looks like it is using this plugin to validate.&amp;nbsp;&lt;A href="https://pypi.org/project/validate-aws-sns-message/" target="_blank" rel="noopener"&gt;https://pypi.org/project/validate-aws-sns-message/&lt;/A&gt;&amp;nbsp; Note, it "Requires message be no older than one hour, the maximum lifetime of an SNS message."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Splunk, it would be much better if this was an optional feature, as it breaks our infrastructure, especially bad since this is a PATCH update, not MAJOR.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 20:18:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581548#M102516</guid>
      <dc:creator>danint</dc:creator>
      <dc:date>2022-01-18T20:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581601#M102524</link>
      <description>&lt;P&gt;I checked Splunkbase, but they do not have version 5.2.1. I know they had this before, but for some reason they reverted it back to version 5.2.0&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 10:04:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581601#M102524</guid>
      <dc:creator>leuorrouel</dc:creator>
      <dc:date>2022-01-19T10:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581606#M102525</link>
      <description>&lt;P&gt;We backed out of the 5.2.1 update.&amp;nbsp; 5.2.0&amp;nbsp; seems to be working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 10:55:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/581606#M102525</guid>
      <dc:creator>parcflyer</dc:creator>
      <dc:date>2022-01-19T10:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: AWS CloudTrail SQS Based S3 error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/634510#M108572</link>
      <description>&lt;P&gt;Hello I'm having the same error, did you manage to fixing it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;2023-03&lt;/SPAN&gt;-&lt;SPAN class=""&gt;15&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;05:26:05&lt;/SPAN&gt;,&lt;SPAN class=""&gt;915&lt;/SPAN&gt; &lt;SPAN class=""&gt;level=WARNING&lt;/SPAN&gt; &lt;SPAN class=""&gt;pid=2768&lt;/SPAN&gt; &lt;SPAN class=""&gt;tid=Thread-7&lt;/SPAN&gt; &lt;SPAN class=""&gt;logger=splunk_ta_aws.modinputs.sqs_based_s3.handler&lt;/SPAN&gt; &lt;SPAN class=""&gt;pos=handler.py:_process:390&lt;/SPAN&gt; | &lt;SPAN class=""&gt;datainput=&lt;/SPAN&gt;"&lt;SPAN class=""&gt;XXXXXX&lt;/SPAN&gt;" &lt;SPAN class=""&gt;start_time=1678855832&lt;/SPAN&gt;, &lt;SPAN class=""&gt;message_id=XXXXXXXXXXXXXXX&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;ttl=300&lt;/SPAN&gt; &lt;SPAN class=""&gt;job_id=XXXXXXXXXXXXX&lt;/SPAN&gt;&amp;nbsp;| &lt;SPAN class=""&gt;message=&lt;/SPAN&gt;"&lt;SPAN class=""&gt;Warning:&lt;/SPAN&gt; &lt;SPAN class=""&gt;This&lt;/SPAN&gt; &lt;SPAN class=""&gt;message&lt;/SPAN&gt; &lt;SPAN class=""&gt;does&lt;/SPAN&gt; &lt;SPAN class=""&gt;not&lt;/SPAN&gt; &lt;SPAN class=""&gt;have&lt;/SPAN&gt; &lt;SPAN class=""&gt;a&lt;/SPAN&gt; &lt;SPAN class=""&gt;valid&lt;/SPAN&gt; &lt;SPAN class=""&gt;SNS&lt;/SPAN&gt; &lt;SPAN class=""&gt;Signature&lt;/SPAN&gt; &lt;SPAN class=""&gt;Message&lt;/SPAN&gt; &lt;SPAN class=""&gt;is&lt;/SPAN&gt; &lt;SPAN class=""&gt;too&lt;/SPAN&gt; &lt;SPAN class=""&gt;old:&lt;/SPAN&gt; &lt;SPAN class=""&gt;2&lt;/SPAN&gt; &lt;SPAN class=""&gt;days&lt;/SPAN&gt;, &lt;SPAN class=""&gt;16:30:10.556919&lt;/SPAN&gt;"&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 05:48:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AWS-CloudTrail-SQS-Based-S3-error/m-p/634510#M108572</guid>
      <dc:creator>splunkoptimus</dc:creator>
      <dc:date>2023-03-15T05:48:00Z</dc:date>
    </item>
  </channel>
</rss>

