Difficulty Provisioning Thingy91 to AWS IoT Fleet Provisioning (Claim Method)

[ItachiVN]

Dear Team,

I am attempting to provision my Thingy91 device to AWS IoT Core using Fleet Provisioning with the Claim method. I've been closely following the instructions in the repository "https://github.com/NordicPlayground/aws-iot-core-fleet-provisioning-with-nrf9160".

Here's a breakdown of my progress and where I'm facing issues:

Steps Completed:

1. Certificate and Key Generation: Successfully generated a provisioning certificate and private key.
2. Connectivity Test: Established a connection with AWS IoT Core using the generated certificate and key with the "Fleet-Provisioning-for-AWS-IoT-embedded-sdk" project. I was able to receive the provisioning certificate and the private key when running the fleet_provisioning_keys_cert demo (running natively on Ubuntu).

Issue: I'm unable to complete the Fleet Provisioning process with the claim method when using the same generated credentials with Thingy91. I'm unsure where the issue lies within the provisioning flow.

Device and Software Details:

• Device: Thingy91
• Modem Firmware Version: v1.3.5
• nRF Connect SDK Version: v2.5.2

Could you kindly help recommend known issues or specific configuration steps I might be missing in the Fleet Provisioning flow for the Thingy91. I would like to attach the project config file, log message console and the modem trace that I collected from the RTT. Thank you in advance for your expertise and assistance.

Sincerely,
Thuan.

#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
# General config
CONFIG_NCS_SAMPLES_DEFAULTS=y
CONFIG_REBOOT=y

# NEWLIB C
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y


# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
# Prioritise NB-IoT
CONFIG_LTE_NETWORK_MODE_NBIOT=y

# Modem library
CONFIG_NRF_MODEM_LIB=y

# Modem key management
CONFIG_MODEM_KEY_MGMT=y

# AWS IoT library
CONFIG_AWS_IOT=y
CONFIG_AWS_IOT_CLIENT_ID_STATIC="thingy91_retry2"
CONFIG_AWS_IOT_BROKER_HOST_NAME="a1tdvh7gznuyl9-ats.iot.ap-southeast-2.amazonaws.com"
CONFIG_AWS_IOT_SEC_TAG=2032024
CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT=2
CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=y
CONFIG_AWS_IOT_LAST_WILL=y
CONFIG_AWS_IOT_TOPIC_GET_ACCEPTED_SUBSCRIBE=y
CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=y
# AWS application config
CONFIG_AWS_IOT_SAMPLE_PUBLICATION_INTERVAL_SECONDS=300
# MQTT - Maximum MQTT keepalive timeout specified by AWS IoT Core
CONFIG_MQTT_KEEPALIVE=1200

# Date Time library
CONFIG_DATE_TIME=y

# Modem information
CONFIG_MODEM_INFO=y

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=8192
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUBOOT_IMG_MANAGER=y

# Image manager
CONFIG_IMG_MANAGER=y
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y
CONFIG_FLASH=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

# AWS FOTA
CONFIG_AWS_FOTA=y
CONFIG_FOTA_DOWNLOAD=y
CONFIG_DFU_TARGET=y

# CJSON
CONFIG_CJSON_LIB=y

# Download client (needed by AWS FOTA)
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096

# Log
CONFIG_LOG=y
CONFIG_AWS_IOT_SAMPLE_LOG_LEVEL_INF=y

# UART Async
# AT Host
CONFIG_UART_0_INTERRUPT_DRIVEN=y
CONFIG_AT_HOST_LIBRARY=y

CONFIG_SERIAL=y
CONFIG_APP_UART=y
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_UARTE1=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n
CONFIG_UART_1_ASYNC=y

CONFIG_AWS_IOT_AUTO_DEVICE_SHADOW_REQUEST=n
CONFIG_AWS_IOT_SAMPLE_LOG_LEVEL_DBG=y

# Enable modem trace via RTT
CONFIG_NRF_MODEM_LIB_TRACE=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y

Fullscreen log_thingy91_aws_iot.txt Download

20:50:19:877 -> �*** Booting nRF Connect SDK v2.5.2 ***
20:50:21:021 -> I: AWS-IoT <-> UART bridge, app version: v1.0.0
20:50:21:255 -> I: Trace thread ready
20:50:21:299 -> I: Trace level override: 2
20:50:21:301 -> I: Subscribed to uplink/2024203/accepted and uplink/2024203/rejected
20:50:23:909 -> +CEREG: 2,"B03D","07CB1E15",9
20:50:23:909 -> I: LTE cell changed: Cell ID: 130752021, Tracking area: 45117
20:50:24:302 -> +CSCON: 1
20:50:24:302 -> I: RRC mode: Connected
20:50:25:840 -> +CEREG: 1,"B03D","07CB1E15",9,,,"11100000","11100000"
20:50:25:840 -> I: Network registration status: Connected - home network
20:50:25:840 -> I: PSM parameter update: TAU: 3240, Active time: -1
20:50:25:866 -> %XTIME: "82","42301231055282","00"
20:50:25:866 -> I: Date time obtained
20:50:25:866 -> I: Next connection retry in 30 seconds
20:50:36:124 -> +CSCON: 0
20:50:36:124 -> I: RRC mode: Idle
20:50:55:868 -> I: Next connection retry in 30 seconds
20:51:25:894 -> I: Next connection retry in 30 seconds
20:51:55:873 -> I: Next connection retry in 30 seconds
20:52:25:876 -> I: Next connection retry in 30 seconds
20:52:55:878 -> I: Next connection retry in 30 seconds
20:53:18:614 -> *** Booting nRF Connect SDK v2.5.2 ***
20:53:18:614 -> I: AWS-IoT <-> UART bridge, app version: v1.0.0
20:53:18:848 -> I: Trace thread ready
20:53:18:858 -> I: Trace level override: 2
20:53:18:874 -> I: Subscribed to uplink/2024203/accepted and uplink/2024203/rejected
20:53:21:028 -> +CEREG: 2,"B03D","07CB1E15",9
20:53:21:028 -> I: LTE cell changed: Cell ID: 130752021, Tracking area: 45117
20:53:21:575 -> +CSCON: 1
20:53:21:575 -> I: RRC mode: Connected
20:53:23:121 -> +CEREG: 1,"B03D","07CB1E15",9,,,"11100000","11100000"
20:53:23:121 -> I: Network registration status: Connected - home network
20:53:23:121 -> I: PSM parameter update: TAU: 3240, Active time: -1
20:53:23:146 -> %XTIME: "82","42301231353282","00"
20:53:23:146 -> I: Date time obtained
20:53:23:146 -> I: Next connection retry in 30 seconds
20:53:33:405 -> +CSCON: 0
20:53:33:405 -> I: RRC mode: Idle
20:53:53:148 -> I: Next connection retry in 30 seconds
20:54:23:151 -> I: Next connection retry in 30 seconds
20:54:49:536 -> I: AWS_IOT_EVT_CONNECTING
20:54:49:891 -> +CSCON: 1
20:54:49:891 -> I: RRC mode: Connected
20:54:53:160 -> W: connection_poll_start failed, error: -119
20:54:53:160 -> E: aws_iot_connect, error: -119
20:54:53:160 -> I: Next connection retry in 30 seconds
20:55:00:904 -> I: AWS_IOT_EVT_DISCONNECTED
20:55:00:904 -> E: Cloud MQTT input error: -128
20:55:11:459 -> +CSCON: 0
20:55:11:459 -> I: RRC mode: Idle
20:55:23:165 -> I: Next connection retry in 30 seconds
20:55:23:165 -> I: AWS_IOT_EVT_CONNECTING
20:55:23:502 -> +CSCON: 1
20:55:23:502 -> I: RRC mode: Connected
20:55:33:905 -> I: AWS_IOT_EVT_DISCONNECTED
20:55:33:905 -> E: Cloud MQTT input error: -128
20:55:44:505 -> +CSCON: 0
20:55:44:505 -> I: RRC mode: Idle
20:55:53:170 -> I: Next connection retry in 30 seconds
20:55:53:170 -> I: AWS_IOT_EVT_CONNECTING
20:55:53:571 -> +CSCON: 1
20:55:53:571 -> I: RRC mode: Connected
20:56:04:904 -> I: AWS_IOT_EVT_DISCONNECTED
20:56:04:904 -> E: Cloud MQTT input error: -128
20:56:15:480 -> +CSCON: 0
20:56:15:480 -> I: RRC mode: Idle
20:56:23:170 -> I: Next connection retry in 30 seconds
20:56:23:170 -> I: AWS_IOT_EVT_CONNECTING
20:56:23:651 -> +CSCON: 1
20:56:23:651 -> I: RRC mode: Connected
20:56:33:990 -> I: AWS_IOT_EVT_DISCONNECTED
20:56:33:990 -> E: Cloud MQTT input error: -128
20:56:44:544 -> +CSCON: 0
20:56:44:544 -> I: RRC mode: Idle
20:56:53:173 -> I: Next connection retry in 30 seconds
20:56:53:173 -> I: AWS_IOT_EVT_CONNECTING
20:56:53:732 -> +CSCON: 1
20:56:53:732 -> I: RRC mode: Connected
20:57:05:807 -> I: AWS_IOT_EVT_DISCONNECTED
20:57:05:807 -> E: Cloud MQTT input error: -128
20:57:16:371 -> +CSCON: 0
20:57:16:371 -> I: RRC mode: Idle
20:57:23:176 -> I: Next connection retry in 30 seconds
20:57:23:176 -> I: AWS_IOT_EVT_CONNECTING
20:57:23:532 -> +CSCON: 1
20:57:23:532 -> I: RRC mode: Connected
20:57:34:225 -> I: AWS_IOT_EVT_DISCONNECTED
20:57:34:225 -> E: Cloud MQTT input error: -128
20:57:44:859 -> +CSCON: 0
20:57:44:859 -> I: RRC mode: Idle
20:57:53:179 -> I: Next connection retry in 30 seconds
20:57:53:179 -> I: AWS_IOT_EVT_CONNECTING
20:57:53:571 -> +CSCON: 1
20:57:53:571 -> I: RRC mode: Connected
20:58:05:194 -> I: AWS_IOT_EVT_DISCONNECTED
20:58:05:194 -> E: Cloud MQTT input error: -128
20:58:15:779 -> +CSCON: 0
20:58:15:779 -> I: RRC mode: Idle
20:58:23:181 -> I: Next connection retry in 30 seconds
20:58:23:181 -> I: AWS_IOT_EVT_CONNECTING
20:58:23:697 -> +CSCON: 1
20:58:23:697 -> I: RRC mode: Connected
20:58:34:887 -> I: AWS_IOT_EVT_DISCONNECTED
20:58:34:887 -> E: Cloud MQTT input error: -128
20:58:45:439 -> +CSCON: 0
20:58:45:439 -> I: RRC mode: Idle
20:58:53:184 -> I: Next connection retry in 30 seconds
20:58:53:184 -> I: AWS_IOT_EVT_CONNECTING
20:58:53:742 -> +CSCON: 1
20:58:53:742 -> I: RRC mode: Connected
20:59:04:710 -> I: AWS_IOT_EVT_DISCONNECTED
20:59:04:710 -> E: Cloud MQTT input error: -128
20:59:15:288 -> +CSCON: 0
20:59:15:288 -> I: RRC mode: Idle
20:59:23:187 -> I: Next connection retry in 30 seconds
20:59:23:187 -> I: AWS_IOT_EVT_CONNECTING
20:59:23:491 -> +CSCON: 1
20:59:23:491 -> I: RRC mode: Connected
20:59:34:184 -> I: AWS_IOT_EVT_DISCONNECTED
20:59:34:184 -> E: Cloud MQTT input error: -128
20:59:44:759 -> +CSCON: 0
20:59:44:759 -> I: RRC mode: Idle
20:59:53:191 -> I: Next connection retry in 30 seconds
20:59:53:191 -> I: AWS_IOT_EVT_CONNECTING
20:59:55:219 -> +CSCON: 1
20:59:55:219 -> I: RRC mode: Connected
21:00:09:639 -> I: AWS_IOT_EVT_DISCONNECTED
21:00:09:639 -> E: Cloud MQTT input error: -128
21:00:20:220 -> +CSCON: 0
21:00:20:220 -> I: RRC mode: Idle
21:00:23:192 -> I: Next connection retry in 30 seconds
21:00:23:192 -> I: AWS_IOT_EVT_CONNECTING
21:00:23:652 -> +CSCON: 1
21:00:23:652 -> I: RRC mode: Connected
21:00:34:950 -> I: AWS_IOT_EVT_DISCONNECTED
21:00:34:950 -> E: Cloud MQTT input error: -128
21:00:45:502 -> +CSCON: 0
21:00:45:502 -> I: RRC mode: Idle
21:00:53:195 -> I: Next connection retry in 30 seconds
21:00:53:195 -> I: AWS_IOT_EVT_CONNECTING
21:00:53:742 -> +CSCON: 1
21:00:53:742 -> I: RRC mode: Connected
21:01:05:127 -> I: AWS_IOT_EVT_DISCONNECTED
21:01:05:127 -> E: Cloud MQTT input error: -128
21:01:15:675 -> +CSCON: 0
21:01:15:675 -> I: RRC mode: Idle
21:01:23:201 -> I: Next connection retry in 30 seconds
21:01:23:201 -> I: AWS_IOT_EVT_CONNECTING
21:01:25:092 -> +CSCON: 1
21:01:25:092 -> I: RRC mode: Connected
21:01:36:774 -> I: AWS_IOT_EVT_DISCONNECTED
21:01:36:774 -> E: Cloud MQTT input error: -128
21:01:47:354 -> +CSCON: 0
21:01:47:354 -> I: RRC mode: Idle
21:01:53:200 -> I: Next connection retry in 30 seconds
21:01:53:200 -> I: AWS_IOT_EVT_CONNECTING
21:01:53:572 -> +CSCON: 1
21:01:53:572 -> I: RRC mode: Connected
21:02:05:256 -> I: AWS_IOT_EVT_DISCONNECTED
21:02:05:256 -> E: Cloud MQTT input error: -128
21:02:15:804 -> +CSCON: 0
21:02:15:804 -> I: RRC mode: Idle
21:02:23:202 -> I: Next connection retry in 30 seconds
21:02:23:202 -> I: AWS_IOT_EVT_CONNECTING
21:02:23:662 -> +CSCON: 1
21:02:23:662 -> I: RRC mode: Connected
21:02:34:158 -> I: AWS_IOT_EVT_DISCONNECTED
21:02:34:158 -> E: Cloud MQTT input error: -128
21:02:44:732 -> +CSCON: 0
21:02:44:732 -> I: RRC mode: Idle
21:02:53:205 -> I: Next connection retry in 30 seconds
21:02:53:205 -> I: AWS_IOT_EVT_CONNECTING
21:02:53:731 -> +CSCON: 1
21:02:53:731 -> I: RRC mode: Connected
21:03:04:999 -> I: AWS_IOT_EVT_DISCONNECTED
21:03:04:999 -> E: Cloud MQTT input error: -128
21:03:15:546 -> +CSCON: 0
21:03:15:546 -> I: RRC mode: Idle
21:03:23:210 -> I: Next connection retry in 30 seconds
21:03:23:224 -> I: AWS_IOT_EVT_CONNECTING
21:03:23:811 -> +CSCON: 1
21:03:23:811 -> I: RRC mode: Connected
21:03:34:449 -> I: AWS_IOT_EVT_DISCONNECTED
21:03:34:449 -> E: Cloud MQTT input error: -128
21:03:45:019 -> +CSCON: 0
21:03:45:019 -> I: RRC mode: Idle
21:03:53:211 -> I: Next connection retry in 30 seconds
21:03:53:211 -> I: AWS_IOT_EVT_CONNECTING
21:03:53:572 -> +CSCON: 1
21:03:53:572 -> I: RRC mode: Connected
21:04:05:905 -> I: AWS_IOT_EVT_DISCONNECTED
21:04:05:905 -> E: Cloud MQTT input error: -128
21:04:16:539 -> +CSCON: 0
21:04:16:539 -> I: RRC mode: Idle
21:04:23:213 -> I: Next connection retry in 30 seconds
21:04:23:213 -> I: AWS_IOT_EVT_CONNECTING
21:04:23:662 -> +CSCON: 1
21:04:23:662 -> I: RRC mode: Connected
21:04:34:630 -> I: AWS_IOT_EVT_DISCONNECTED
21:04:34:630 -> E: Cloud MQTT input error: -128
21:04:45:184 -> +CSCON: 0
21:04:45:184 -> I: RRC mode: Idle
21:04:53:216 -> I: Next connection retry in 30 seconds
21:04:53:216 -> I: AWS_IOT_EVT_CONNECTING
21:04:53:731 -> +CSCON: 1
21:04:53:731 -> I: RRC mode: Connected
21:05:05:064 -> I: AWS_IOT_EVT_DISCONNECTED
21:05:05:064 -> E: Cloud MQTT input error: -128
21:05:15:659 -> +CSCON: 0
21:05:15:659 -> I: RRC mode: Idle
21:05:23:219 -> I: Next connection retry in 30 seconds
21:05:23:219 -> I: AWS_IOT_EVT_CONNECTING
21:05:23:811 -> +CSCON: 1
21:05:23:811 -> I: RRC mode: Connected
21:05:35:944 -> I: AWS_IOT_EVT_DISCONNECTED
21:05:35:944 -> E: Cloud MQTT input error: -128
21:05:46:498 -> +CSCON: 0
21:05:46:498 -> I: RRC mode: Idle
21:05:53:221 -> I: Next connection retry in 30 seconds
21:05:53:221 -> I: AWS_IOT_EVT_CONNECTING
21:05:53:582 -> +CSCON: 1
21:05:53:582 -> I: RRC mode: Connected
21:06:05:519 -> I: AWS_IOT_EVT_DISCONNECTED
21:06:05:519 -> E: Cloud MQTT input error: -128
21:06:16:090 -> +CSCON: 0
21:06:16:090 -> I: RRC mode: Idle
21:06:23:224 -> I: Next connection retry in 30 seconds
21:06:23:224 -> I: AWS_IOT_EVT_CONNECTING
21:06:25:251 -> +CSCON: 1
21:06:25:251 -> I: RRC mode: Connected
21:06:37:159 -> I: AWS_IOT_EVT_DISCONNECTED
21:06:37:159 -> E: Cloud MQTT input error: -128
21:06:47:745 -> +CSCON: 0
21:06:47:745 -> I: RRC mode: Idle
21:06:53:227 -> I: Next connection retry in 30 seconds
21:06:53:227 -> I: AWS_IOT_EVT_CONNECTING
21:06:53:731 -> +CSCON: 1
21:06:53:731 -> I: RRC mode: Connected
21:07:17:985 -> +CSCON: 0
21:07:17:985 -> I: RRC mode: Idle
21:07:23:234 -> W: connection_poll_start failed, error: -119
21:07:23:234 -> E: aws_iot_connect, error: -119
21:07:23:234 -> I: Next connection retry in 30 seconds
21:07:53:244 -> W: connection_poll_start failed, error: -119
21:07:53:244 -> E: aws_iot_connect, error: -119
21:07:53:244 -> I: Next connection retry in 30 seconds
21:08:10:531 -> +CSCON: 1
21:08:10:531 -> I: RRC mode: Connected
21:08:21:664 -> +CSCON: 0
21:08:21:664 -> I: RRC mode: Idle
21:08:23:253 -> W: connection_poll_start failed, error: -119
21:08:23:253 -> E: aws_iot_connect, error: -119
21:08:23:253 -> I: Next connection retry in 30 seconds
21:08:53:263 -> W: connection_poll_start failed, error: -119
21:08:53:263 -> E: aws_iot_connect, error: -119
21:08:53:263 -> I: Next connection retry in 30 seconds
21:09:23:272 -> W: connection_poll_start failed, error: -119
21:09:23:272 -> E: aws_iot_connect, error: -119
21:09:23:272 -> I: Next connection retry in 30 seconds
21:09:53:282 -> W: connection_poll_start failed, error: -119
21:09:53:282 -> E: aws_iot_connect, error: -119
21:09:53:282 -> I: Next connection retry in 30 seconds

0728.RTTLogger_Channel_modem_trace.log

[Markus Tacker (he/him)]

Fleet provisioning requires the device to interact with AWS' provisioning MQTT API: https://docs.aws.amazon.com/iot/latest/developerguide/fleet-provision-api.html

This is not implement in nRF Connect SDK and you have to implement this yourself.

[ItachiVN]

Thank you for the information Markus, from my understanding, it's just about connecting to AWS using claim credentials and then subscribing and publishing to a specified topic to obtain a new certificate and private key. I've connected to AWS using the claim credentials generated from the workaround (https://github.com/NordicPlayground/aws-iot-core-fleet-provisioning-with-nrf9160) using AWS-IOT-SDK-C, but I can't connect to AWS IoT using the same claim credentials with my thing91 and nRF connect SDK (connection_poll_start failed, error: -119 or Cloud MQTT input error: -128)

[Markus Tacker (he/him)]

Please have a look at the policy, it only allows the device to publish and subscribe to a specific topic.

However, your firmware configuration of aws_iot causes the application to subscribe and publish to other topics as well.

Because this is not allowed by the provisioning credentials policy, the connection gets terminated.

[ItachiVN]

Hello Markus,
Thank you for your prompt reply. I tried to turn off subscribing for all possible topics (shadow + application topics) and comment on all the code that might be published to the AWS IoT but the problem remains (Cloud MQTT input error: -128)


I also read some posts about the "Cloud MQTT input error: -128" and found out there is a high chance there is a problem with the certificate. So I take some other attempts.

1. I tried and was able to connect to AWS IoT (different regions and credentials) with my Thingy91 to make sure there were no problems with the hardware and cellular connection.

2. I loaded the claim certificate generated from the workaround to my ESP32 project as well as the fleet provisioning demo using AWS-IOT-SDK-C and was able to make them connect to the AWS IoT. I also go 1 step further by checking the credentials stored inside my thingy91 by comparing the SHA256 of the CA cert, device cert, and private key.

Could you please help take a look at the following details:

thingy91_aws_trace.log

Fullscreen 3603.device_log.txt Download

I: AWS-IoT <-> UART bridge, app version: v1.0.0
+CEREG: 2,"B03D","07CB2617",9
I: LTE cell changed: Cell ID: 130754071, Tracking area: 45117
+CSCON: 1
I: RRC mode: Connected
+CEREG: 1,"B03D","07CB2617",9,,,"11100000","11100000"
I: Network registration status: Connected - home network
I: PSM parameter update: TAU: 3240, Active time: -1
%XTIME: "82","42303201357482","00"
I: Date time obtained
I: Next connection retry in 15 seconds
I: AWS_IOT_EVT_CONNECTING
I: AWS_IOT_EVT_DISCONNECTED
E: Cloud MQTT input error: -128
I: Next connection retry in 15 seconds
I: AWS_IOT_EVT_CONNECTING
17:54:11:552 -> I: AWS_IOT_EVT_DISCONNECTED
17:54:11:552 -> E: Cloud MQTT input error: -128
17:54:16:217 -> I: Next connection retry in 15 seconds
17:54:16:217 -> I: AWS_IOT_EVT_CONNECTING
17:54:26:632 -> I: AWS_IOT_EVT_DISCONNECTED
17:54:26:632 -> E: Cloud MQTT input error: -128
17:54:31:220 -> I: Next connection retry in 15 seconds
17:54:31:220 -> I: AWS_IOT_EVT_CONNECTING
17:54:41:631 -> I: AWS_IOT_EVT_DISCONNECTED
17:54:41:631 -> E: Cloud MQTT input error: -128
17:54:46:223 -> I: Next connection retry in 15 seconds
17:54:46:223 -> I: AWS_IOT_EVT_CONNECTING
17:54:56:637 -> I: AWS_IOT_EVT_DISCONNECTED
17:54:56:637 -> E: Cloud MQTT input error: -128
17:55:01:226 -> I: Next connection retry in 15 seconds
17:55:01:226 -> I: AWS_IOT_EVT_CONNECTING
17:55:11:594 -> I: AWS_IOT_EVT_DISCONNECTED
17:55:11:594 -> E: Cloud MQTT input error: -128
17:55:16:229 -> I: Next connection retry in 15 seconds
17:55:16:229 -> I: AWS_IOT_EVT_CONNECTING
17:55:26:792 -> I: AWS_IOT_EVT_DISCONNECTED
17:55:26:792 -> E: Cloud MQTT input error: -128
17:55:31:233 -> I: Next connection retry in 15 seconds
17:55:31:233 -> I: AWS_IOT_EVT_CONNECTING
17:55:41:886 -> I: AWS_IOT_EVT_DISCONNECTED
17:55:41:886 -> E: Cloud MQTT input error: -128
17:55:46:236 -> I: Next connection retry in 15 seconds
17:55:46:236 -> I: AWS_IOT_EVT_CONNECTING
17:55:58:366 -> I: AWS_IOT_EVT_DISCONNECTED
17:55:58:366 -> E: Cloud MQTT input error: -128
17:56:01:239 -> I: Next connection retry in 15 seconds
17:56:01:239 -> I: AWS_IOT_EVT_CONNECTING
17:56:16:247 -> W: connection_poll_start failed, error: -119
17:56:16:247 -> E: aws_iot_connect, error: -119
17:56:16:247 -> I: Next connection retry in 15 seconds
17:56:31:257 -> W: connection_poll_start failed, error: -119
17:56:31:257 -> E: aws_iot_connect, error: -119
17:56:31:257 -> I: Next connection retry in 15 seconds
17:56:37:512 -> I: AWS_IOT_EVT_DISCONNECTED
17:56:37:512 -> E: Cloud MQTT input error: -128
17:56:46:263 -> I: Next connection retry in 15 seconds
17:56:46:263 -> I: AWS_IOT_EVT_CONNECTING
17:56:58:957 -> I: AWS_IOT_EVT_DISCONNECTED
17:56:58:957 -> E: Cloud MQTT input error: -128
17:57:01:267 -> I: Next connection retry in 15 seconds
17:57:01:267 -> I: AWS_IOT_EVT_CONNECTING
17:57:11:752 -> I: AWS_IOT_EVT_DISCONNECTED
17:57:11:752 -> E: Cloud MQTT input error: -128
17:57:16:270 -> I: Next connection retry in 15 seconds
17:57:16:270 -> I: AWS_IOT_EVT_CONNECTING
17:57:26:557 -> I: AWS_IOT_EVT_DISCONNECTED
17:57:26:557 -> E: Cloud MQTT input error: -128
17:57:31:273 -> I: Next connection retry in 15 seconds
17:57:31:273 -> I: AWS_IOT_EVT_CONNECTING

Kconfig changes belong with comment all publish/subscribe calls:

# Additional Kconfig options
CONFIG_AWS_IOT_AUTO_DEVICE_SHADOW_REQUEST=n
CONFIG_AWS_IOT_TOPIC_GET_ACCEPTED_SUBSCRIBE=n
CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=n
CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=n
CONFIG_MQTT_CLEAN_SESSION=y

[Markus Tacker (he/him)]

Please consult the AWS IoT Lifecycle events for your device to see what causes the disconnect: docs.aws.amazon.com/.../life-cycle-events.html