Problems with programming device certificates from the AWS IoT console.

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Thu, 23 Sep 2021 11:03:38 GMT

Yes, the last answer offered a solution to my problem.

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Thu, 23 Sep 2021 07:23:44 GMT

Awesome!

Could you accept one of the answers as a solution?

Thank you!

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Wed, 22 Sep 2021 15:29:13 GMT

After verifying and correcting the cloud side permissions (especially the attachment of the policy to my thing's certificate), the problem has been resolved and I was able to run and test the sample: AWS_iot without any problem.

Thank you for your assistance in resolving this problem.

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Wed, 22 Sep 2021 13:46:37 GMT

That's progress.

Did you also verify the cloud side permissions? Especially that the policy is attached to your thing's certificate?

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Tue, 21 Sep 2021 16:26:53 GMT

1. I did double-check and subsequently I corrected the entry for the configuration of the AWS IoT broker, using the address string found under "Rest API Endpoint" in the AWS IoT Console under: IoT core>Manage>things>interact.

2. I double-checked and I corrected the entry for the configuration of the AWS_IoT_Client_ID_Static, using the name of the thing as it appears in the AWS IoT Console under: IoT core>Manage>things.

3. I double-checked that the entry for the configuration of the AWS_IOT_SEC_TAG is 201.

However, after I have built the the AWS_iot sample and I tried to run it, the following error messages appeared on the LTE Link Monitor every 30 seconds:

AWS_IOT_EVT_CONNECTING

connection_poll_start failed, error:-119

aws_iot_connect, error:-119

Next connection retry in 30 seconds

AWS_IOT_EVT_DISCONNECTED

Next connection retry in 30 seconds

as can be seen on the attached log file from the LTE Link Monitor.

devzone.nordicsemi.com/.../2021_2D00_09_2D00_21-LTE-Link-Monitor-log-file.txt

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Tue, 21 Sep 2021 13:03:38 GMT

You cannot connect to example.com, this is a reserved domain name which does not resolve.
The aws_iot sample requires you to configure the hostname of your AWS IoT broker via CONFIG_AWS_IOT_BROKER_HOST_NAME, please double check that it is correct.

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Tue, 21 Sep 2021 12:21:36 GMT

1. what kind of SIM card are you using in the device? A Vodacom SIM card, enabled for NB-IoT in the Republic of South Africa.

2. did you activate the SIM card? Yes

3. did you double check that you have sufficient data available on the SIM card? Yes

I was able to successfully run and test the application: asset_tracker , connecting successfully to the nrfcloud.com but I could not connect to www.example.com when I tried to run and test the sample: https_client.

I was told that when I ran the sample: https_client, it was unsuccessfully trying to establish a TCP connection via port 443 (which is the HTTPS port number) because server was denying the request with a TCP RST (reset of TCP connection).

On the other hand, when I ran the sample:asset_tracker, it was running via MQTTS on port 8883 and it did successfully connect to nrfcloud.com.

Could the problem that I am experiencing with connecting to the internet while running sample: AWS_IoT be similar to the one that I experienced with sample: https_client?

Does the sample: AWS_IoT require establishing a TCP connection via port 443 (which is the HTTPS port number)?

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Tue, 21 Sep 2021 11:12:40 GMT

It looks like you are not getting a connection to the internet, because getaddrinfo fails.

what kind of SIM card are you using in the device?
did you activate the SIM card?
did you double check that you have sufficient data available on the SIM card?

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Mon, 20 Sep 2021 15:25:06 GMT

Hi Markus,

Thanks for clarifying that by copy&paste you mean that I should first open the file with a text editor. Once I did that, I was able to copy&paste the device certificates without any problems.

While the device certificates from AWS IoT Console have now been programmed correctly, I am still experiencing problems when running the sample: AWS_iot and trying to connect to the AWS IoT client broker, with the following messages popping up on the LTE Link Monitor every 30 seconds:

AWS_IOT_EVT_CONNECTING

getaddrinfo, error:-11

client_broker_init, error:-10

as shown in the attached LTE Link Monitor log file.

devzone.nordicsemi.com/.../2021_2D00_09_2D00_20-LTE-Link-Monitor-log-file.txt

Are you able to assist with this problem or shall I open a new ticket for it?

Regards,

Jacek

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Mon, 20 Sep 2021 13:21:03 GMT

Hei Jacek,

just to clarify:

can you type in the text boxes?
with copy&paste we mean that you should
1. open the file with a text editor (e.g. Notepad on Windows)
2. select the entire content
3. copy it to the clipboard
4. switch to the Certificate manager
5. paste into the respective textbox

It pasted content should look like this:

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Mon, 20 Sep 2021 13:05:31 GMT

Hi Markus,

As I explained in my earlier communications, I did follow this procedure "as documented here" several times but my attempts to use copy-and-paste in order to enter the required certificates from a folder: c:\Nordic to the relevant text boxes of the Certificate Manager were unsuccessful. I was able to copy a certificate from the folder c:\Nordic but there was no response when I tried to paste this certificate into the relevant text box of the Certificate Manager.

I tried to attach the copies of these 3 certificates that I downloaded from the AWS IoT Console (to a C;\Nordic folder of my PC) to this message for your reference but I could not insert them into this message.

Regards,

Jacek

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Mon, 20 Sep 2021 12:32:39 GMT

I sounds like you are not actually using a JSON file (one with a .json extension), but dragging over the individual certificate files.

You need to copy&paste them individually in the text boxes, as documented here.

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Mon, 20 Sep 2021 12:05:38 GMT

Hi Markus,

As requested, I enclose a screenshot of UI , where I tried to provide/enter the device certificate into the correct entry box of the Certificate Manager:

devzone.nordicsemi.com/.../Screenshot-20_2D00_09_2D00_2021.docx

I also enclose a screenshot of the error console:

devzone.nordicsemi.com/.../Screenshot-of-the-error-console-20_2D00_09_2D00_2021.docx

The error message: "Unexpected number in JSON at position 1" appears in the log of the Certificate Manager when I try to enter the device certificate using the drag-and-drop method or when I use "Load from JSON" option.

When I try to use copy-and-paste to enter the device certificate into the correct entry box of the Certificate Manager - there is no response at all.

Regards,

Jacek

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Mon, 20 Sep 2021 08:30:42 GMT

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.

[quote userid="104491" url="~/f/nordic-q-a/79742/problems-with-programming-device-certificates-from-the-aws-iot-console/330142#330142"]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?[/quote]

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.

RE: Problems with programming device certificates from the AWS IoT console.

Jacek Majda — Sun, 19 Sep 2021 20:21:16 GMT

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

RE: Problems with programming device certificates from the AWS IoT console.

Markus Tacker (he/him) — Fri, 17 Sep 2021 07:57:20 GMT

Hei Jacekma,

which application are you running? The pre-programmed sample only works with nRF Cloud.
I'd recommend to start with the aws_iot sample, it will walk you through the steps to connect to AWS IoT.