Unknown Host Error

0

I'm working on a proof-of concept project for a customer. It will connect to AWS IoT to send device logs to S3.

To test that the device can handle the activity, I'm starting with the AWS embedded C SDK. My workflow is to build the code for an x86-64 Linux host for testing and debug. Then, I move the code to another workspace where I cross-compile it for the embedded device, a 32-bit ARM-based Linux device.

Up to yesterday, the subscribe-publish sample was working successfully on both my development system and the target device.

Yesterday, I created a new thing in a different region from the original (moved from us-east-2 to us-east-1) so I could access some of the customer's AWS Lambda rules. I updated my device certificates and keys as well as the endpoint in the sample program header file. Since the move, I'm unable to connect to the AWS IoT service in either us-east-1 or us-east-2.

When I run the sample code, I get the following output (name and id redacted):

DEBUG: iot_tls_connect L#161 . Connecting to arn:aws:iot:us-east-1:3071:thing/******/8883...
ERROR: iot_tls_connect L#164 failed
! mbedtls_net_connect returned -0x52

ERROR: main L#190 Error(-23) connecting to arn:aws:iot:us-east-1:****3071:thing/***********:8883

As part of my debug effort, I deleted all my things and certificates and created from scratch this morning. I'm at a bit of a loss as to what to do next.

The device, certificate and attached policy show up in the console.

Just to check out the keys and strings I put them in the Python AWS sample program and had a failure to connect as well.

Not sure what I'm missing. Need some guidance.

Thanks.

Edited by: GaryKB on Aug 6, 2020 10:35 AM

GaryKB
已提问 4 年前213 查看次数
2 回答
0

Found the issue.
Used bad endpoint nema.

GaryKB
已回答 4 年前
0

Found the issue.
Used bad endpoint name.

GaryKB
已回答 4 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则