<?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 Python.log errors after upgrade to Victoria in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Python-log-errors-after-upgrade-to-Victoria/m-p/688178#M114619</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;After upgrading from Classic to Victoria Experience on our Splunk Cloud stack, we have encountered issues retrieving data from AWS SQS-based S3. The inputs remained after the migration, but for some, it seems the SQS queue name is missing. When we try to configure these inputs, we immediately receive a 404 error in the python.log. Please see the screenshot below for reference.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-05-21 173549.png" style="width: 532px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/30893i45E70DA06FDEA5A4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-05-21 173549.png" alt="Screenshot 2024-05-21 173549.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Furthermore, the error message indicates that the SQS queue may not be present in the given region. However, we have confirmed that the queue does exist in the specified region. Has anyone else experienced this issue and can offer assistance?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 21 May 2024 14:40:52 GMT</pubDate>
    <dc:creator>roberto_baggio</dc:creator>
    <dc:date>2024-05-21T14:40:52Z</dc:date>
    <item>
      <title>Python.log errors after upgrade to Victoria</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Python-log-errors-after-upgrade-to-Victoria/m-p/688178#M114619</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;After upgrading from Classic to Victoria Experience on our Splunk Cloud stack, we have encountered issues retrieving data from AWS SQS-based S3. The inputs remained after the migration, but for some, it seems the SQS queue name is missing. When we try to configure these inputs, we immediately receive a 404 error in the python.log. Please see the screenshot below for reference.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-05-21 173549.png" style="width: 532px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/30893i45E70DA06FDEA5A4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-05-21 173549.png" alt="Screenshot 2024-05-21 173549.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Furthermore, the error message indicates that the SQS queue may not be present in the given region. However, we have confirmed that the queue does exist in the specified region. Has anyone else experienced this issue and can offer assistance?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 14:40:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Python-log-errors-after-upgrade-to-Victoria/m-p/688178#M114619</guid>
      <dc:creator>roberto_baggio</dc:creator>
      <dc:date>2024-05-21T14:40:52Z</dc:date>
    </item>
  </channel>
</rss>

