• State Not Answered
  • Replies 8 replies
  • Subscribers 68 subscribers
  • Views 519 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 329506
Options

publishing or subscribing to topic aws/certificates/create/json and aws/certificates/create/json/accepted fails with POLLHUP error to end up with aws iot disconnect event

Omkar Prabhu

I am trying to get provisioning by trusted user procedure of aws_iot working by making some changes in aws_iot nrf sample 

I have tested it with permanent certificates and it works fine


But Whenever I try to connect to aws iot server with these topic 


aws/certificates/create/json

aws/certificates/create/json/accepted

it fails with POLLHUP error, ending client connection be it with permanent certificates or with temp certificates (Used in provisioning by trusted device procedure)

Referring to similar issue I figured it has to do with Modem's limitation on handling big TLS buffers that are sent in response to this topic
( Issue Link: aws iot disconnect event when publishing to $aws/certificates/create/json )

Can we configure it, if not how can we develop a code where we can fetch permanent certs using temp certs with nrf platforms?

P.S. I am using the same aws_iot sample just changed the endpoint, client id and topics

Also I have made sure that AWS side things (provisioning template, policies etc.) are fine as it works for provisioning by trusted user for native ubuntu emulation of the device

Parents Reply
  • 0 in reply to Hakon

    Thanks for Validating the issue and pointing out to this PR, which SDK version it's compatible with?
    The reason why I asked is while trying to integrate I faced some issues compiling modem key management lib as it is, (haven't done any changes in that)

    In file included from D:/v2.6.1/nrf/samples/net/aws_iot/src/main.c:19:
    D:/v2.6.1/nrf/include/modem/modem_key_mgmt.h:13:10: fatal error: nrf_socket.h: No such file or directory
    13 | #include <nrf_socket.h>
    | ^~~~~~~~~~~~~~

    The file exists at given path but this blog post suggests it has to do with CMake changes related to board

    I am trying to build it for 7002dk ns would that be a problem?

Children
No Data
Related