Problems with programming device certificates from the AWS IoT console.

[Jacek Majda]

I did download the device certificates from the AWS IoT console into a directory: C:\Nordic  on my PC.

However, my attempts to copy and paste these device certificates from the directory C:\Nordic on my PC to the respective entries (CA Certificate, Client Certificate and Private Key) on the Certificate Manager of the LTE Link Monitor were unsuccessful. No response at all...

Also, when you open the Certificate Manager in the LTE Link Monitor, you see the following note: "Use security tag 16842753 to manage nRF Connect for Cloud certificate, otherwise pick a different tag".   So, which security tag shall be used to manage the AWS IoT certificates?

I am using:

1. nRF9160DK v1.0.1

2. Windows 10 Pro OS, version: 20H2, OS build:19042.631

3. nRF Connect v 3.7.0

4. nRF Connect SDK v1.6.1

Regards,

Jacek

[Jacek Majda]

Hey Markus,

I am in fact using the aws_iot sample and I did follow the steps given in this sample on how to connect to AWS IoT, .

I did set up an AWS account, created a thing in AWS IoT, generated the required certificates and downloaded them to the directory C:\Nordic on my PC.

However, my attempts to copy and paste these device certificates from the directory C:\Nordic on my PC to the respective entries (CA Certificate, Client Certificate and Private Key) on the Certificate Manager of the LTE Link Monitor were unsuccessful. No response at all...Just a message: "Unexpected number in JSON at position 1" appears in the log on the "Certificate Manager" page of the LTE Link Monitor.

Also, when you open the Certificate Manager in the LTE Link Monitor, you see the following note: "Use security tag 16842753 to manage nRF Connect for Cloud certificate, otherwise pick a different tag".   So, which security tag shall be used to manage the AWS IoT certificates?

Regards,

Jacek

[Markus Tacker (he/him)]

Hei Jacek,

the "Unexpected number in JSON at position 1" sounds either like a copy and paste issue, or a problem with the certificate manager.

Could you paste a screenshot of the UI where you provide your certificate, and also a screenshot of the error console: press Ctrl+Shift+i to open the console, you should see an error message there.

Jacek Majda said:

Also, when you open the Certificate Manager in the LTE Link Monitor, you see the following note: "Use security tag 16842753 to manage nRF Connect for Cloud certificate, otherwise pick a different tag".   So, which security tag shall be used to manage the AWS IoT certificates?

You can set the sec tag in the configuration: https://github.com/nrfconnect/sdk-nrf/blob/3e1f601eb6c13d9a6189505fab0bc7ee1e4670fe/samples/nrf9160/aws_iot/prj.conf#L34

The default is 201.