<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124683/thingy-91x-aws-iot-failure</link><description>I have succesfully tested my software that sends gnss location to aws iot with nrf9151dk. Recently I configured software also support also thingy91x. My problem is that Aws iot connection drops shortly after connection with following logs: 
 [00:00:24</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 Nov 2025 13:14:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124683/thingy-91x-aws-iot-failure" /><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/554124?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2025 13:14:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e131e8ce-0a5a-4857-9b11-31c4bdfeedc1</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;You can try this basic policy;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;{
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;,
  &amp;quot;Statement&amp;quot;: [
    {
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;,
      &amp;quot;Action&amp;quot;: &amp;quot;iot:*&amp;quot;,
      &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot;
    }
  ]
}&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/553696?ContentTypeID=1</link><pubDate>Fri, 07 Nov 2025 14:06:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0398271-0ef9-4b2b-b198-7244de290dfb</guid><dc:creator>odik</dc:creator><description>&lt;p&gt;Currrently only&amp;nbsp;iot:Connect and iot:Publish are used. Connection is lost even if nothing else is done after connecting to broker.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/553252?ContentTypeID=1</link><pubDate>Tue, 04 Nov 2025 08:19:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b24c1449-89f2-4dba-8c0b-ed5ae8501284</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;What AWS policy are you using?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/552393?ContentTypeID=1</link><pubDate>Sat, 25 Oct 2025 10:13:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4708a1b0-76c3-4b6a-857b-7f2eeed9a302</guid><dc:creator>odik</dc:creator><description>&lt;p&gt;They are already enabled and disconnect is casused by&amp;nbsp;&lt;span&gt;&amp;quot;disconnectReason&amp;quot;: &amp;quot;CLIENT_ERROR&amp;quot;. According to AWS IoT documentation this error is caused by client doing something wrong. However I haven&amp;#39;t been able to figure out why is that. Completly identical code works without&amp;nbsp;&lt;/span&gt;errors in nRF9151DK but still problem persist only with Thingy.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/552131?ContentTypeID=1</link><pubDate>Wed, 22 Oct 2025 09:38:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3faf6615-e805-4a8a-9fde-b2042aea0f19</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Can you enable&amp;nbsp;&lt;span&gt;&lt;a title="https://docs.aws.amazon.com/iot/latest/developerguide/life-cycle-events.html" href="https://docs.aws.amazon.com/iot/latest/developerguide/life-cycle-events.html"&gt;AWS IoT lifecycle events&lt;/a&gt;&lt;/span&gt;&amp;nbsp;to check if the disconnect is caused by a policy issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/551960?ContentTypeID=1</link><pubDate>Mon, 20 Oct 2025 13:54:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d22a5502-413d-48e2-8cd6-9c115f61e74b</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Thanks, I don&amp;#39;t see any clear cause. But I have forwarded the trace to the modem team so they can also have a look.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/551873?ContentTypeID=1</link><pubDate>Sun, 19 Oct 2025 13:30:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4cf7689-ae7c-4d99-9c6b-5d92b88f7bc8</guid><dc:creator>odik</dc:creator><description>&lt;p&gt;Sorry for the delay, I have been busy with other projects. Modem trace is now added to attachments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy 91x aws iot failure</title><link>https://devzone.nordicsemi.com/thread/550130?ContentTypeID=1</link><pubDate>Tue, 30 Sep 2025 10:24:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ac18ad5c-516d-46f9-8e28-6168de27a5ad</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;can you please provide a modem trace, and make sure that the failed connection attempt is part of it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>