<?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>Asset tracker v2 based application stopped communicating with AWS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/83974/asset-tracker-v2-based-application-stopped-communicating-with-aws</link><description>I have experimented with asset_tracker_v2 sample application using Cat Tracker sample in AWS. In addition I have created my own application which uses the same JITP certificate mechanism. For some reason the certificates are not working anymore. My Thingy91</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Jan 2022 08:44:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/83974/asset-tracker-v2-based-application-stopped-communicating-with-aws" /><item><title>RE: Asset tracker v2 based application stopped communicating with AWS</title><link>https://devzone.nordicsemi.com/thread/349450?ContentTypeID=1</link><pubDate>Tue, 25 Jan 2022 08:44:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee8c0f5b-8dc7-4d0c-ad80-3744b2f4a551</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Happy to hear that you solved the issue!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Asset tracker v2 based application stopped communicating with AWS</title><link>https://devzone.nordicsemi.com/thread/349358?ContentTypeID=1</link><pubDate>Mon, 24 Jan 2022 17:34:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb1a0691-687c-461e-b640-faa91b00ca0a</guid><dc:creator>Hidastelija</dc:creator><description>&lt;p&gt;Looks like there are two different things. The issue in AWS IoT Console has something to do with &amp;quot;New console experience&amp;quot; as the problem in the console is present only the new console experience is on.&lt;/p&gt;
&lt;p&gt;The connectivity issue may have been something in the AWS end. The problem has just gone away this afternoon.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>