<?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 Addon for Splunk doesn't recognize config messages in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/AWS-Addon-for-Splunk-doesn-t-recognize-config-messages/m-p/498764#M61369</link>
    <description>&lt;P&gt;Ah.  the input type of "Config" expects me to subscribe it to an sqs fed by an sns that gets real time changes to the config data.  What  set up was an SQS based S3 bucket, which is a different option when you create it.&lt;/P&gt;</description>
    <pubDate>Sun, 22 Mar 2020 19:59:59 GMT</pubDate>
    <dc:creator>jarrell</dc:creator>
    <dc:date>2020-03-22T19:59:59Z</dc:date>
    <item>
      <title>AWS Addon for Splunk doesn't recognize config messages</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/AWS-Addon-for-Splunk-doesn-t-recognize-config-messages/m-p/498763#M61368</link>
      <description>&lt;P&gt;I'm not getting anything in my config input, even though I know events are logging.  I started searching _internal and found that if I watch splunk_ta_aws.modinputs.config I can see the sqs processing.  WHenever a messages pops up in the queue, splunk says it's not a config record.  Example:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;2020-03-22 19:06:17,736 level=WARNING pid=11190 tid=MainThread logger=splunk_ta_aws.modinputs.config pos=__init__.py:_stream_events:344 | datainput="Config_0bd7b668-1857-4466-9977-1595a2745bf3" | message="Invalid notifications have been removed from SQS : {"Records":[{"eventVersion":"2.1","eventSource":"aws:s3","awsRegion":"us-east-2","eventTime":"2020-03-22T19:06:16.660Z","eventName":"ObjectCreated:Put","userIdentity":{"principalId":"AWS:XXXXXXXXXXXXXX"},"requestParameters":{"sourceIPAddress":"172.18.xx.xxx"},"responseElements":{"x-amz-request-id":"03FF16BD00681075","x-amz-id-2":"redacted"},"s3":{"s3SchemaVersion":"1.0","configurationId":"Put config notice","bucket":{"name":"correct bucket name for config data","ownerIdentity":{"principalId":"XXXXXXXXXXXXX"},"arn":"arn:aws:s3:::correct bucket name for config data"},"object":{"key":"aws-config/AWSLogs/436617320021/Config/ConfigWritabilityCheckFile","size":0,"eTag":"d41d8cd98f00b204e9800998ecf8427e","versionId":"M5RCgK646j6EJPn5MGNeMYhbzRbh8Bge","sequencer":"005E77B7289FBE2097"}}}]}"&lt;/CODE&gt; &lt;/P&gt;

&lt;P&gt;I'm not sure how to diagnose from here!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 04:40:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/AWS-Addon-for-Splunk-doesn-t-recognize-config-messages/m-p/498763#M61368</guid>
      <dc:creator>jarrell</dc:creator>
      <dc:date>2020-09-30T04:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: AWS Addon for Splunk doesn't recognize config messages</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/AWS-Addon-for-Splunk-doesn-t-recognize-config-messages/m-p/498764#M61369</link>
      <description>&lt;P&gt;Ah.  the input type of "Config" expects me to subscribe it to an sqs fed by an sns that gets real time changes to the config data.  What  set up was an SQS based S3 bucket, which is a different option when you create it.&lt;/P&gt;</description>
      <pubDate>Sun, 22 Mar 2020 19:59:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/AWS-Addon-for-Splunk-doesn-t-recognize-config-messages/m-p/498764#M61369</guid>
      <dc:creator>jarrell</dc:creator>
      <dc:date>2020-03-22T19:59:59Z</dc:date>
    </item>
  </channel>
</rss>

