Can’t connect with AWS IoT sample with own CA

RE: Can’t connect with AWS IoT sample with own CA

Amanda Hsieh — Tue, 11 Mar 2025 16:00:43 GMT

Please create a new support case for the latest issue, which is away from the original scope.

RE: Can’t connect with AWS IoT sample with own CA

GilDev — Tue, 11 Mar 2025 09:16:51 GMT

Hi,

Thank you for the precisions. Our design uses a nRF9160 with a Microchip ENC424J600 Ethernet controller. Is there a way to use the modem’s IP stack with our external controller? We’ve been struggling for months to embed MbedTLS and make all the libs (mostly socket calls) use it or use the modem’s stack depending on if we want to start an Ethernet or LTE connection.

RE: Can’t connect with AWS IoT sample with own CA

Amanda Hsieh — Mon, 10 Mar 2025 16:59:31 GMT

Hi,

Unfortunately, there is no such resource as your requirement. The samples/net/aws_iot sample supports Wi-Fi and LTE depending on the board that it is built for. The sample supports the nRF7002 DK, which uses the 53 as host and 7002 that implements lower level wifi protocol, for LTE it uses the nRF91DK. 7002: Memory size might be an issue if the user intends to add a lot of custom logic. Partly due to RAM requirements of the Wi-Fi stack and MBEDTLS needing to run on the application core. 91: A lot more leeway due to the IP stack (TCP/IP and TLS) running on the modem.

-Amanda H.

RE: Can’t connect with AWS IoT sample with own CA

GilDev — Mon, 10 Mar 2025 10:55:38 GMT

Thanks, there was indeed an issue around this! I can’t get it to work with MbedTLS though, but it seems that the sample removed the overlay that allowed it to work using MbedTLS instead of the modem’s internal TLS stack in recent SDK versions, is there any information about this somewhere?

RE: Can’t connect with AWS IoT sample with own CA

Amanda Hsieh — Wed, 05 Mar 2025 13:47:38 GMT

Hi,

See the TroubleShooting for Error code -128.

Regards,
Amanda H.